
Accessibility testing checks whether people with different disabilities can use a digital product, service, or document. A tester may examine keyboard navigation, screen reader behavior, captions, forms, color contrast, zoom, error messages, and task completion. The work can sit within quality assurance, product design, user research, compliance, or a specialist accessibility team.
There is no single tool that proves a product is accessible. Automated checks can catch some code and contrast issues, but human review is needed to understand whether the experience works in context. This guide explains how to explore the career, practice responsibly, build a portfolio, and prepare applications. Accessibility standards and legal duties vary by product and jurisdiction; this article is career guidance, not a compliance determination.
Understand the role and its boundaries
Accessibility testers help teams identify barriers and communicate them clearly. A task might be impossible to complete with a keyboard, a screen reader may announce controls in an unhelpful order, or a video may lack captions. The tester records the environment, steps, expected behavior, actual behavior, user impact, and evidence. A team may then prioritize fixes based on user impact, applicable standards, product context, and available information.
Job titles include accessibility tester, digital accessibility analyst, QA accessibility specialist, accessibility consultant, and inclusive design researcher. Some roles require deep technical knowledge of HTML, mobile accessibility APIs, or assistive technology. Others focus on testing workflows and reporting. Read the posting for required tools, platforms, standards, and qualifications.
Accessibility work should not treat disabled people as a single group or assume what a person can do. Different people use different combinations of keyboard, speech input, magnification, captions, screen readers, switches, and other tools. A tester can report what they observed and recommend involving users with relevant lived experience when the team needs broader evidence.
Build a foundation in accessible design
Learn the basic principles behind accessible web content: information should be perceivable, operable, understandable, and robust. Study how semantic structure, labels, headings, focus order, keyboard access, text alternatives, captions, color contrast, and error messages affect interaction. W3C's Web Accessibility Initiative provides tutorials for writing, designing, and developing more accessible websites.
Understand the difference between a standard, a test method, and a tool. WCAG describes success criteria at defined conformance levels. A checklist may help organize a review, while an automated scanner may report potential issues. Neither alone establishes that every user task works or that a product legally complies. Identify the applicable version and scope before making a claim.
Practice with assistive technologies and operating system features. Start by testing a small page using only a keyboard. Check visible focus, skip navigation, form labels, error recovery, and whether you can complete the main task. Then inspect how a screen reader announces controls and headings. Use magnification and zoom to see if content reflows or becomes hidden. Follow tool documentation and avoid presenting one device or test setup as universal coverage.
Run a bounded and repeatable evaluation
Choose a public page or a project you own, and define the scope: which page, task, browser, operating system, and assistive technology are included. Use ordinary public interactions and respect the site’s terms. Do not submit real personal data, create test accounts on a service without permission, or probe sensitive features. For a portfolio, a simple page you built yourself is safest.
Write down the user goal before you start. For example: “A visitor can find the hours and contact details for a service.” Complete the task using keyboard-only input, then another accessibility feature or assistive technology. Record each action, what was announced or shown, and where the experience became difficult. If a task completes, note any extra effort or confusing behavior rather than marking the entire page “accessible.”
A useful issue report names a concise title, environment, steps, expected and actual results, impact, and evidence. Example: “Keyboard focus disappears after closing the search dialog in the sample page; pressing Tab moves to a location that is not visible.” Avoid dramatic or vague labels. State the observed behavior and connect it to the task someone cannot complete.
Distinguish a confirmed issue from a suggestion. If the behavior depends on a particular browser and technology combination, report the setup. If you are unsure which standard applies, say what needs expert review. A good report helps the team reproduce and understand the problem without claiming more than the test showed.
Make a credible portfolio
Use two or three carefully documented examples rather than a long list of automated screenshots. One can be a keyboard evaluation, another a form-label and error-message review, and a third an accessible component you built and tested. Include the scope, environment, methods, results, limitations, and next steps. If you tested a real site, confirm that your report and screenshots may be shared.
For a design or code sample, explain your choices. Show a labeled form, visible focus state, descriptive link text, or a dialog that returns focus appropriately. Include keyboard instructions and test notes. Avoid claiming full WCAG compliance based on a small self-review. You can say “I checked these selected behaviors against these criteria in this environment,” then list what you did not evaluate.
Credit source code, libraries, icons, and collaborators. Remove names, contact details, authentication tokens, and any private user information from screenshots. If you use synthetic test content, label it. Make the portfolio itself navigable by keyboard, readable at zoom, and accessible enough that your presentation does not contradict your subject.
Work with users and teams respectfully
Accessibility testing intersects with design, engineering, quality assurance, legal, support, and product management. Explain an issue in terms of the task and barrier, then discuss possible fixes with the people who own the component. There may be several valid implementations. A tester's recommendation should help the team decide, not insist that one implementation is the only possible solution without evidence.
When research includes people with disabilities, plan access and consent carefully. Provide an accessible invitation and materials, explain the purpose, ask permission before recording, and offer a way to participate that does not create unnecessary burden. Compensate participants fairly when possible and protect their information. Follow organizational research and privacy procedures.
Be careful when describing user needs. Avoid speaking for a whole disability group based on one session. Report participant feedback in context and invite direct perspectives from people who use the relevant technology. The role is to improve products with users, not make assumptions on their behalf.
Translate existing experience
QA, front-end development, design, technical writing, customer support, and research can all provide relevant skills. A tester might bring disciplined defect reporting; a designer might understand interaction patterns; a support agent may know where people become confused. Describe the work you actually performed and which accessibility techniques you are now learning.
If you have lived experience with a disability or assistive technology, sharing it is a personal choice. You do not owe an employer private medical details. You can focus on skills, tools, and work examples. If you need an interview accommodation, ask for it through the employer's stated process without providing more information than necessary.
Apply and prepare for interviews
Search for accessibility QA, digital accessibility, inclusive design, accessibility analyst, and related roles. Read for specific standards, platforms, and testing methods. Some employers expect certification; others value work samples and practical knowledge. Check who maintains credentials and whether the job actually requests one before spending money.
In an interview, you may be asked to evaluate a component. Clarify the context and task, identify a test environment, describe keyboard and assistive technology checks, and explain how you would record an issue. If a question asks whether something “passes,” explain the scope and limits of the evidence rather than giving an absolute answer from one test.
Ask how accessibility is integrated in design and development, how issues are prioritized, what assistive technology is available, who reviews standards interpretations, and whether the team involves disabled users. Ask how new employees receive training. These questions can reveal whether accessibility work is supported throughout the product lifecycle.
A three-week portfolio exercise
Week 1: select a small page you own or can evaluate lawfully. Define the task, environment, and selected accessibility checks. Week 2: perform keyboard and screen reader checks, write reproducible findings, and ask another person to review the clarity of your reports.
Week 3: fix one issue in a project you control, retest it, and document what changed. Add a limitations section and references to applicable guidance. Do not claim broad conformance from this exercise; the point is to demonstrate a careful method and an ability to learn.
Common questions
Do I need to be a developer? Some roles require coding; others focus on evaluation, research, or reporting. Technical skills expand options, but follow the actual requirements of your target jobs.
Can an automated scanner certify a website? No. Scanners can identify some potential problems, but they do not replace manual testing, assistive technology review, and user research where appropriate.
Should I get an accessibility certification? It may be useful when employers request it or when you need structured learning. Check current prerequisites, cost, scope, and renewal rules.
Can I report accessibility issues to any public website? You can provide respectful feedback through public support channels, but do not run intrusive tests or publish sensitive findings without considering the site's policies and user safety.
Portfolio checklist
- Scope, task, environment, methods, and limitations are stated.
- Reports separate observation, impact, and proposed fix.
- You tested more than one interaction mode where appropriate.
- Any user research follows consent and privacy requirements.
- All screenshots and code are safe to share and properly credited.
- Your own portfolio supports keyboard access and readable presentation.
Accessibility testing is a practical career built on careful observation and respectful collaboration. W3C guidance can provide a starting point, while current standards, product requirements, and local laws determine the details of a real evaluation. Show a bounded method, explain the limits of what you tested, and keep learning from people who use the technology.
0 Comments