Skip to content
View v-mlakshmanm's full-sized avatar

Block or report v-mlakshmanm

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
v-mlakshmanm/README.md

Hi, I'm M.L.M.Manikanta

Accessibility Tester | HTML, CSS & JavaScript

My focus is on making web experiences accessible and usable for everyone, including people with disabilities. I combine accessibility testing with front-end technologies to identify barriers and support practical fixes.

Accessibility Focus

  • WCAG 2.2: Evaluate web experiences against Level A and AA success criteria.
  • Keyboard accessibility: Review navigation, focus order, visible focus, and keyboard traps.
  • Screen reader testing: Check accessible names, roles, states, and content structure.
  • Visual accessibility: Review color contrast, text resizing, reflow, and non-color cues.
  • Forms and interactions: Check labels, instructions, validation messages, and dynamic updates.
  • Issue reporting: Document reproduction steps, user impact, relevant WCAG criteria, and recommended fixes.

Front-End Technologies

Technology Accessibility Focus
HTML Semantic elements, heading structure, landmarks, descriptive links, alternative text, and labeled forms.
CSS Visible focus indicators, readable layouts, responsive reflow, sufficient contrast, and reduced-motion preferences.
JavaScript Keyboard-operable interactions, focus management, accessible validation, and appropriate announcements for dynamic content.

Testing Approach

  1. Understand the user journey and expected behavior.
  2. Use automated checks to identify potential accessibility issues.
  3. Test manually with a keyboard and screen reader, including zoom and reflow checks.
  4. Report actionable findings and collaborate on fixes.
  5. Retest changes and check for regressions.

Automated checks support accessibility testing, but do not replace manual evaluation or establish WCAG conformance on their own.

Let's Collaborate

I'm interested in accessible web interfaces, inclusive design, and front-end accessibility improvements.

Pinned Loading

  1. skills-deploy-to-azure skills-deploy-to-azure Public

    My clone repository

    JavaScript

  2. react react Public

    Forked from v-QuamrulSiddiqui/react

    The library for web and native user interfaces

    JavaScript 2

  3. skills-code-with-codespaces skills-code-with-codespaces Public

    My clone repository

    HTML