46 topics
Foundation and General KnowledgeDocs ↗
Types of Disabilities
Disabilities include visual (blindness, low vision), hearing (deafness, hard of hearing), motor (mobility issues, dexterity), cognitive (learning disabilities, intellectual), neurological (autism, ADHD), and invisible disabilities (chronic illness, mental health).
Keywords
disabilityvisualhearingmotorcognitiveneurologicalinvisible disability
Accessibility must account for all disability types. Many disabilities are invisible — not all disabilities are permanent or static.
Foundation and General KnowledgeDocs ↗
Americans with Disabilities Act (ADA) - 1990
Federal civil rights law prohibiting discrimination against individuals with disabilities in all areas of public life. Covers employment (Title I), state/local government (Title II), and public accommodations/private business (Title III).
Keywords
ADA1990civil rightslegislationdiscriminationUSATitle ITitle IITitle III
The ADA requires reasonable accommodations in employment and accessibility in public spaces. Digital accessibility was clarified in 2010 with ADA amendments.
Foundation and General KnowledgeDocs ↗
Section 508 of the Rehabilitation Act - 1998
US federal law requiring federal agencies to make their electronic and information technology (ICT) accessible to employees and the public with disabilities.
Keywords
Section 5081998federalICTinformation technologygovernmentrehabilitation act
Section 508 applies to all federal agencies and organizations receiving federal funding. It is often the strictest accessibility standard in the US.
Foundation and General KnowledgeDocs ↗
Rehabilitation Act of 1973
Federal law ensuring individuals with disabilities receive vocational rehabilitation and other support services. Section 504 prohibits discrimination based on disability by any organisation receiving federal funding.
Keywords
Rehabilitation Act1973vocationalfederal fundingcivil rightsSection 504
Broader than the ADA — applies to any entity receiving federal dollars. Often overlooked but covers many organisations.
Foundation and General KnowledgeDocs ↗
UN Convention on the Rights of Persons with Disabilities (CRPD) - 2006
International human rights treaty affirming the rights of persons with disabilities to participate fully in society. Establishes accessibility as a human right, not a privilege.
Keywords
CRPD2006UNinternationalhuman rightsglobalratification
Signed by 184 countries. Influences accessibility standards globally. Emphasises the social model of disability and reasonable accommodation.
Foundation and General KnowledgeDocs ↗
Web Content Accessibility Guidelines (WCAG) 2.1
International standard for web accessibility published by the W3C. Provides guidelines to make web content more accessible to people with disabilities.
Keywords
WCAG2.1W3Cweb standardsprinciplesguidelinesaccessibilitylevels A AA AAA
WCAG 2.1 has 4 principles (POUR), 13 guidelines, and 78 success criteria at three levels: A (minimum), AA (standard), AAA (enhanced). Expanded WCAG 2.0 with mobile accessibility.
Foundation and General KnowledgeDocs ↗
EN 301 549 - European Accessibility Standard
European standard for accessibility of ICT products and services. Used by EU member states for public procurement and regulatory compliance.
Keywords
EN 301 549EuropeanICTaccessibilityEUstandardpublic procurement
Aligns with WCAG 2.1 but also covers hardware, software, and services. More comprehensive than WCAG alone.
Foundation and General Knowledge
Social Model vs Medical Model of Disability
Social Model: disability is caused by societal barriers and lack of accessibility, not by individual limitations. Medical Model: disability is a medical condition to be 'fixed' or treated.
Keywords
social modelmedical modeldisabilitybarriersinclusionperson-firstidentity-first
Accessibility advocates largely favour the social model — focus is on removing barriers, not 'fixing' disabled people. Language matters: 'person with a disability' (medical) vs 'disabled person' (social/identity-first).
Related: Universal Design, Inclusive Design
Foundation and General KnowledgeDocs ↗
Universal Design Principles
Design philosophy that makes products and environments usable by the widest range of people, regardless of age, ability, or status. Seven core principles guide the approach.
Keywords
universal designdesign for allinclusive designprinciples7 principlescurb cuts
Curb cuts benefit everyone — not just wheelchair users. Design for disability benefits all users (captions help in noisy environments, alt text helps image search, etc.)
Related: Inclusive Design, Accessible Design
Foundation and General Knowledge
Assistive Technology (AT) Overview
Tools and devices that help people with disabilities use technology. Includes screen readers, magnifiers, voice control, eye-tracking, switch devices, and AAC (augmentative and alternative communication).
Keywords
assistive technologyATscreen readermagnifiervoice controlswitch controlaugmentative alternative communication
AT can be hardware or software. Web accessibility standards enable AT to work properly — inaccessible websites break AT functionality.
Related: JAWS, NVDA, VoiceOver, Magnification, Speech-to-Text
Accessible Design and Development
WCAG Principle 1: Perceivable
Information and user interface components must be perceivable to users. Includes alternative text for images, captions for audio/video, sufficient colour contrast, and distinguishable foreground/background.
Keywords
perceivableWCAGprinciple 1alternative textcaptionscontrastdistinguishable
Perceivable means users must be able to perceive the information — not just via one sensory mode. Content must be available in multiple formats.
Related: Alt Text, Captions, Transcripts, Colour Contrast, Text Sizing
Accessible Design and Development
WCAG Principle 2: Operable
User interface components and navigation must be operable. Users must be able to navigate using keyboard, have enough time to read/interact, avoid content that causes seizures, and navigate efficiently.
Keywords
operableWCAGprinciple 2keyboardnavigationtimingseizuresfocus
Operability means users can control the interface without a mouse. Keyboard accessibility is essential — all functionality must be reachable via keyboard.
Related: Keyboard Navigation, Focus Management, Skip Links, Timeouts, Flashing Content
Accessible Design and Development
WCAG Principle 3: Understandable
Information and operation must be understandable. Text must be readable, language must be clear, pages must be predictable, and users must get help with input errors.
Keywords
understandableWCAGprinciple 3readabilitylanguagepredictabilityinput assistance
Content should be written clearly, use plain language, provide definitions for jargon, and give clear error messages with suggestions for correction.
Related: Plain Language, Readability, Error Messages, Page Structure, Form Labels
Accessible Design and Development
WCAG Principle 4: Robust
Content must be robust enough to be interpreted by assistive technologies. Requires valid HTML, proper semantic markup, and ARIA labels where needed.
Keywords
robustWCAGprinciple 4compatibilityassistive technologyHTMLARIAsemantic markup
Robust means code is written correctly and follows standards. Assistive technologies rely on proper code structure to convey meaning.
Related: HTML Semantics, ARIA, Validation, Assistive Technology Compatibility
Accessible Design and Development
Alternative Text (Alt Text)
Text description of images that conveys meaning and function. Essential for screen reader users. Decorative images should have empty alt (alt=''), functional images need descriptive alt.
Keywords
alt textalternative textimagesdescriptivescreen readersdecorativefunctional images
Alt text should be concise (~125 characters) and describe the image's purpose, not just say 'image'. For complex images (charts, diagrams), provide description elsewhere on page.
Related: Descriptive Text, Long Descriptions, Image Complexity, Charts and Diagrams
Accessible Design and Development
Captions and Transcripts for Multimedia
Video requires captions (text of all dialogue and sound effects) and transcripts. Audio requires transcripts. Described video provides narration of visual elements for blind users.
Keywords
captionstranscriptsvideoaudioclosed captionsopen captionsdescribed video
Captions are NOT subtitles — they include sound effects and speaker identification. Live video requires real-time captions (CART or live captions). Transcripts enable searching and provide alternative access.
Related: CART, Live Captions, Audio Description, Described Video, Media Players
Accessible Design and Development
Colour Contrast Requirements
Text must have sufficient contrast with its background. WCAG AA requires 4.5:1 for normal text, 3:1 for large text (18pt+). AAA requires 7:1 and 4.5:1 respectively.
Keywords
colour contrastcolor contrastWCAG4.5:13:1luminositycontrast ratioreadability
Contrast is measured using luminosity ratio. Not about colour alone — a red on red with high luminosity difference passes. Use contrast checkers to verify.
Related: WebAIM Contrast Checker, Luminosity, Readability, Colour Blindness Simulation
Accessible Design and Development
Keyboard Navigation and Focus
All functionality must be accessible via keyboard. Focus must be visible and logical. Tab order must follow logical flow. Avoid keyboard traps where users can't escape via keyboard.
Keywords
keyboardnavigationtab orderfocusfocus visiblefocus trapskip links
Tab key moves forward through focusable elements; Shift+Tab moves backward. Focus indicator must be visible (don't remove the outline without replacing it). Skip links bypass repetitive navigation.
Related: Tab Order, Focus Visible, Skip Links, Focus Trap, Focus Management
Accessible Design and Development
Accessible Forms
Forms must have properly associated labels, use fieldsets for grouped fields, provide clear error messages, and indicate required fields. Placeholder text alone is insufficient as a label.
Keywords
formslabelsfieldsetlegendrequirederror messagesvalidationplaceholder
Labels must be programmatically associated with inputs using <label> element or aria-label. Error messages should identify the field and suggest correction.
Related: Form Labels, Error Identification, Validation Messages, Autocomplete
Accessible Design and Development
Semantic HTML Markup
Use HTML elements for their intended purpose: headings for structure, nav for navigation, main for primary content, etc. Semantic HTML provides meaning that assistive technologies can interpret.
Keywords
semantic HTMLHTML5heading levelsnavmainarticleasidelandmark regions
Avoid using divs for everything. Proper heading hierarchy (h1, h2, h3...) helps screen reader users navigate. Landmark regions (nav, main, aside) enable quick navigation.
Related: HTML5 Elements, Heading Structure, Landmark Regions, Navigation Structure
Accessible Design and Development
ARIA (Accessible Rich Internet Applications) Basics
ARIA attributes provide information to assistive technologies when semantic HTML is insufficient. Includes roles (what something is), states (current condition), and properties (characteristics).
Keywords
ARIArolesstatespropertiesaria-labelaria-describedbyaria-livecustom widgets
ARIA is a supplement, not a replacement for semantic HTML. 'No ARIA is better than bad ARIA.' Use native HTML first, ARIA only when necessary for custom components.
Related: ARIA Roles, ARIA States, ARIA Properties, Live Regions, Widget Patterns
Accessible Design and Development
Responsive Design and Mobile Accessibility
Responsive design must work on all screen sizes. Touch targets must be 44x44px minimum. Content must reflow without horizontal scrolling. Users must be able to zoom to 200%.
Keywords
responsivemobiletouch targetsviewportzoomreflowtext resizing
Mobile accessibility includes ensuring text is resizable, touch targets are large enough, and content reflows to fit smaller screens. Avoid fixed layouts that break with zoom.
Related: Touch Targets, Viewport Meta Tag, Text Resizing, Portrait/Landscape, One-Handed Use
Accessible Design and Development
Accessible PDF Documents
PDFs must be tagged with proper structure, include alternative text for images, have logical reading order, and make form fields accessible. Scanned PDFs require OCR.
Keywords
PDFaccessible PDFtagsreading orderalternative textform fieldsOCR
Many PDFs are inaccessible because they're untagged. Tools like Adobe Acrobat can add tags, but clean source documents are better. Avoid images of text.
Related: PDF Tags, Reading Order, Form Fields in PDFs, OCR, Alternatives to PDF
Accessible Design and Development
Accessible Office Documents
Office documents must use proper heading styles, include alt text for images, use table headers, and have logical reading order. Avoid formatting for meaning (bold instead of styles).
Keywords
WordExcelPowerPointGoogle Docsdocument structureheading stylesalt texttable headers
Users may need to convert documents to other formats (HTML, Braille, etc.). Proper structure enables conversion. Built-in accessibility checkers help identify issues.
Related: Heading Styles, Table Headers, Reading Order, Document Conversion
Testing and Audit
Manual Accessibility Testing
Testing without automated tools — using keyboard to navigate, using screen readers to verify content, and manually checking against WCAG guidelines.
Keywords
manual testingkeyboard testingscreen reader testingvisual inspectionuser testing
Manual testing is essential because automated tools catch ~30% of issues. Include keyboard-only users, screen reader users, and people testing their own tools (if disabled).
Related: Screen Reader Testing, Keyboard Navigation Testing, WCAG Compliance Testing, User Testing with Disabled Users
Testing and Audit
Automated Accessibility Testing Tools
Tools like axe, Lighthouse, and WAVE automatically scan for common accessibility issues. Can catch technical errors quickly but miss context-dependent issues.
Keywords
automated testingaxeLighthouseWAVEPaciello GroupPa11ytools
Automated tools are useful for catching low-hanging fruit (missing alt text, low contrast, form labels) but cannot test user experience or semantic meaning. Use in conjunction with manual testing.
Related: axe DevTools, Lighthouse, WAVE, Pa11y, Contrast Checkers
Testing and Audit
Screen Reader Testing
Testing with actual screen readers (NVDA, JAWS on Windows; VoiceOver on Mac/iOS; TalkBack on Android). Requires learning screen reader controls and testing with real users.
Keywords
screen readerNVDAJAWSVoiceOvernarratortestingkeyboard shortcuts
Screen readers interpret code structure and read content aloud. Testing reveals issues like missing alt text, improper heading levels, inaccessible forms, and broken ARIA.
Related: NVDA, JAWS, VoiceOver, TalkBack, Screen Reader Commands
Testing and Audit
WCAG Compliance Audit Process
Systematic evaluation of a website or application against WCAG criteria. Involves sampling pages, testing against guidelines, documenting issues, and assigning severity levels.
Keywords
auditWCAG auditcomplianceassessmentsamplingreportingremediation
Audits typically result in a report categorizing issues as Critical (complete failure), Major (significant barrier), or Minor (minor inconvenience). Guides remediation priorities.
Related: Audit Methodology, Issue Severity, Remediation Planning, Re-testing, Ongoing Monitoring
Testing and Audit
Testing with Real Users (Disabled Users)
Testing with actual people with disabilities — the gold standard. Reveals issues that automated tools and experts miss. Participants use their own assistive technology and workflows.
Keywords
user testingdisabled usersusability testingfeedbackinsightsauthentic testing
'Nothing about us without us' — include disabled people in design and testing. Real user testing often uncovers unexpected barriers and usage patterns.
Related: Inclusive User Testing, Disabled User Panels, Accessibility Research, Feedback Loops
Testing and Audit
WCAG Conformance Levels (A, AA, AAA)
WCAG has three conformance levels. Level A = minimum (18 criteria), AA = standard (22 additional criteria, ~28 total), AAA = enhanced (11 additional criteria, ~39 total).
Keywords
conformance levelslevel Alevel AAlevel AAAWCAGcompliance levelspriority
AA is the standard most organisations target. AAA includes some subjective criteria (precise language, simplified language) that are hard to measure consistently.
Related: Success Criteria, Conformance Claims, Partial Conformance, Lawful Compliance
Testing and Audit
WCAG 2.1 Success Criteria Overview
78 specific, testable success criteria across 13 guidelines and 4 principles. Each criterion has a level (A, AA, or AAA) and sufficient techniques for compliance.
Keywords
success criteriaWCAG78 criteriatestablemeasurableconformancesufficient techniques
Success criteria are the actionable benchmarks. Each has intent, examples, and related techniques. Familiarity with relevant criteria is essential for compliance work.
Related: Sufficient Techniques, Advisory Techniques, Failures, Intent Statements
Assistive Technology
Screen Readers
Software that reads text aloud and enables Braille output. Converts visual content to auditory or tactile. Used by blind and low-vision users.
Keywords
screen readerspeech synthesisBraille displayNVDAJAWSVoiceOverTalkBack
Common screen readers: NVDA (free, Windows), JAWS (paid, Windows), VoiceOver (built-in, Mac/iOS), TalkBack (built-in, Android). Each has different keyboard commands and verbosity levels.
Related: Speech Synthesis, Braille Displays, Virtual Cursor, Focus Mode, Screen Reader Detection
Assistive Technology
Magnification Software
Software that enlarges screen content. Used by people with low vision to see text and images. Can magnify up to 60x or more.
Keywords
magnificationscreen magnifierlow visionzoommagnifybuilt-inthird-party
Some magnification tools include word highlighting, colour inversion, and crosshairs to track cursor. Built-in options exist on Windows (Magnifier) and Mac (Zoom).
Related: Zoom Function, Colour Inversion, Cursor Tracking, Built-in Magnification
Assistive Technology
Voice Control and Speech Recognition
Software allowing users to control computers via voice commands and dictation. Used by people with motor disabilities, chronic pain, or repetitive strain injuries.
Keywords
voice controlspeech recognitionhands-freevoice commandsdictationmotor disability
Options include Dragon NaturallySpeaking (paid), built-in OS speech recognition, and browser-based tools. Works best with accessible web design (proper ARIA labels, logical navigation).
Related: Dictation, Voice Commands, Command Languages, Accuracy Challenges
Assistive Technology
Switch Control and Alternative Input Devices
Hardware and software for users with severe motor disabilities. Single switches, eye-gaze trackers, and head pointers enable computer control without traditional keyboard/mouse.
Keywords
switch controlsingle switchsip-and-puffeye gazehead pointermotor disability
Switch control works by cycling through focusable items. Requires proper keyboard navigation and focus management in applications. Eye-gaze technology is increasingly affordable.
Related: Single Switch Access, Eye-Gaze Technology, Head Tracking, Dwell Selection
Assistive Technology
Live Captioning and Real-Time Text
Real-time text conversion of spoken content. CART (Communications Access Realtime Translation) is used for meetings/presentations. Live captions appear on devices in real-time.
Keywords
live captionCARTreal-time textdeaf accessrelayinstant messagingTTYL
Some phones have built-in live captions. Video platforms like YouTube auto-generate captions. Professional CART stenographers provide 98%+ accuracy for events.
Related: CART Services, Auto-Captions, Accuracy, Speaker Identification
Assistive Technology
Colour Blindness and Vision Simulation Tools
Tools simulating colour blindness types to help designers test colour dependence. Also filter/adjustment tools for people with colour vision deficiency.
Keywords
colour blindnesscolor blindnessdeuteranopiaprotanopiatritanopiaachromatopsiasimulation
Types: red-blind (protanopia), green-blind (deuteranopia), blue-yellow blind (tritanopia), complete (achromatopsia). Simulators help designers avoid colour-only indicators.
Related: Simulation Tools, Colour Blind Palette, Texture/Pattern Instead of Colour
Management and Leadership
Accessibility Statements and Conformance Claims
Public declaration of accessibility compliance and any known limitations. Provides contact information for accessibility issues. Shows organisational commitment.
Keywords
accessibility statementconformance claimWCAGtransparencyknown limitationscontact information
Should include conformance level claimed, date of assessment, known limitations, and how to report issues. Example: 'This website conforms to WCAG 2.1 Level AA'.
Related: Transparency, Accountability, Known Issues List, Remediation Timeline
Management and Leadership
Accessibility Policies and Standards
Organisational policies mandating accessibility in all projects. Includes procurement standards, development guidelines, and testing requirements.
Keywords
accessibility policystandardsguidelinesorganisationalprocurementtechnology selection
Strong policies require accessibility audits before launch, accessibility training for teams, and budget allocation for remediation. Policies should specify conformance level (usually AA).
Related: Procurement Standards, Technology Standards, Development Guidelines, Budget Planning
Management and Leadership
Accessibility Team Structure and Roles
Organisational structure for managing accessibility. May include accessibility coordinators, auditors, training leads, and developer advocacy. Requires clear ownership.
Keywords
accessibility teamrolescoordinatorsauditorstrainingresponsibilitymaturity
Accessibility is everyone's job but needs central coordination. Mature organisations embed accessibility experts in design, development, and QA teams.
Related: Accessibility Champion, Distributed Responsibility, Embedded Expertise, Governance
Management and Leadership
Accessibility Training and Awareness
Ongoing education ensuring all staff understand accessibility importance. Includes role-specific training (designers learn WCAG design, developers learn HTML/ARIA, etc.).
Keywords
trainingawarenesseducationdesign thinkingdevelopmentall teamscontinuous learning
Training should be regular and role-specific. Should cover why accessibility matters (legal, ethical, business) and practical implementation.
Related: Onboarding Training, Specialist Certification, Awareness Campaigns, Lunch-and-Learns
Management and Leadership
Accessibility Budget and Resource Planning
Allocating budget for accessibility — tools, training, staffing, and remediation. Building accessibility in from the start is cheaper than retrofitting.
Keywords
budgetcostROIremediationtrainingtoolsstaffingplanning
Budget should cover: testing tools (licenses for automated testing), training, audits, hiring expertise, and remediation work. Prevention is cheaper than cure.
Related: Cost-Benefit Analysis, Prevention vs Remediation, Tool Licenses, Staffing Models
Management and Leadership
Legal Liability and Litigation Trends
Legal risk of inaccessible websites under ADA and other laws. Growing litigation trend in US. Non-compliance can result in lawsuits and significant penalties.
Keywords
legalliabilityADA litigationlawsuitscomplianceriskinsurance
Under ADA Title III, inaccessible websites are considered discrimination. Settlements often reach six figures. The business case for accessibility includes legal risk mitigation.
Related: Legal Risk, Litigation, Settlement Amounts, Proactive Compliance
Management and Leadership
Measuring Accessibility Progress and Metrics
Defining metrics to track accessibility maturity. May include: % pages audited, issues resolved, user satisfaction, WCAG conformance level achieved.
Keywords
metricsmeasurementKPIprogressgoalscompliance ratesuser satisfaction
Avoid vanity metrics. Focus on business outcomes: reduced support tickets, improved user retention, expanded market access. Track both compliance and user satisfaction.
Related: Key Performance Indicators (KPI), Maturity Models, User Research, Satisfaction Surveys
Management and Leadership
Managing Vendor and Third-Party Accessibility
Ensuring third-party tools, plugins, and services meet accessibility standards. Requires contractual requirements and evaluation before integration.
Keywords
vendorthird-partySaaSprocurementaccessibility requirementscontractsescrow
Many inaccessible websites are built with inaccessible plugins/themes. Vendor selection should include accessibility requirements. Request accessibility documentation and conduct testing.
Related: Procurement Criteria, Accessibility Questionnaires, Contract Language, Risk Assessment
Management and Leadership
International Accessibility Standards and Regulations
Accessibility standards vary globally. EU has EN 301 549, Canada has AODA, Australia has DDA. CRPD influences many countries. International organisations must navigate multiple standards.
Keywords
internationalCRPDEN 301 549AODAATAGregulationsglobal compliance
Global organisations often target WCAG AA + applicable regional standards. EN 301 549 is more comprehensive than WCAG alone. Local laws may be stricter than international standards.
Related: Regional Regulations, Compliance Strategy, Multi-Standard Approach