
Knowledge Base Accessibility: WCAG, Testing, Content, and Procurement Guide
Knowledge Base Accessibility is the practice of making a knowledge system’s content, search, navigation, interactive components, authoring tools, media, files, and support paths usable by people with disabilities across devices, input methods, and assistive technologies.
An accessible knowledge base is not limited to adding alternative text to images or checking color contrast. It must support the complete journey: reaching the help center, identifying the page, searching or browsing, evaluating results, reading an article, following instructions, completing a form, accessing a file, recovering from an error, and reaching human assistance when self-service is not enough.
Accessibility also applies to the people who create and maintain the knowledge. The reader-facing help center may be usable while the article editor, media library, analytics dashboard, approval workflow, or theme settings remain inaccessible to disabled authors and administrators.
Practical rule: Evaluate the entire knowledge experience, not only the article body or default theme. Content, templates, search, permissions, files, widgets, authoring tools, and support escalation all affect whether a person can complete the intended task.
| Term | What it means | What it does not prove |
|---|---|---|
| Accessibility | The extent to which people with disabilities can perceive, understand, navigate, interact with, and contribute to the knowledge experience | That every applicable law, contract, policy, or standard has been satisfied |
| Usability | How effectively, efficiently, and satisfactorily intended users complete defined tasks | That disability-related barriers have been identified or removed |
| WCAG conformance | A determination that defined web content meets the applicable WCAG success criteria and conformance requirements | Universal legal compliance or usability for every person and context |
| Legal compliance | Meeting the laws, regulations, contracts, procurement terms, and policies applicable to an organization | That one WCAG version or one audit answers every legal question |
| ACR | An Accessibility Conformance Report documenting how a product supports applicable accessibility criteria | Independent certification that the configured implementation is fully accessible |
| VPAT | A standardized template commonly used to create an ACR | The completed accessibility report itself |
| ATAG | Guidance for making authoring tools accessible and helping authors create accessible content | Reader-interface conformance by itself |
Contents
- Which accessibility standards apply?
- The five layers of knowledge base accessibility
- Map the complete accessible user journey
- Page structure, landmarks, and orientation
- Accessible search, suggestions, and results
- Navigation and consistent help
- Keyboard operation and focus management
- Visual presentation, zoom, reflow, and mobile use
- Cognitive accessibility and plain language
- Accessible knowledge article design
- Images, screenshots, audio, video, tables, and code
- Accessible PDFs and downloadable documents
- Forms, errors, authentication, and restricted content
- Authoring-tool and administration accessibility
- Mobile, embedded, in-app, and AI delivery
- Custom themes, plugins, localization, and third parties
- How to test Knowledge Base Accessibility
- Report and prioritize accessibility defects
- Evaluate accessible knowledge base software
- Governance and implementation roadmap
- Knowledge Base Accessibility checklist
- Sources checked
Which Accessibility Standards Apply to a Knowledge Base?
Use current authoritative sources rather than assuming that one standard, product statement, or automated score answers every accessibility question. A knowledge base may be subject to technical standards, organizational policies, contractual requirements, procurement rules, and laws that reference different versions of WCAG.
Use WCAG 2.2 as the current technical reference
The W3C WCAG overview presents WCAG 2.2 as the latest version in the WCAG 2 series. WCAG 2.2 became a W3C Recommendation on October 5, 2023 and includes nine success criteria added after WCAG 2.1.
For a new or redesigned knowledge base, WCAG 2.2 is a sensible current technical reference unless a law, contract, policy, or procurement requirement specifies another target. Relevant WCAG 2.2 additions include:
- Focus Not Obscured
- Focus Appearance
- Dragging Movements
- Target Size (Minimum)
- Consistent Help
- Redundant Entry
- Accessible Authentication
Review the W3C summary of changes in WCAG 2.2 before defining the project’s conformance target.

Do not confuse the latest WCAG version with every U.S. legal requirement
Some current U.S. requirements reference earlier WCAG versions. For example, the U.S. Department of Justice’s ADA Title II rule for state and local government web content and mobile applications uses WCAG 2.1 Level AA, not WCAG 2.2.
Current ADA.gov guidance for state and local governments lists these compliance dates:
- April 26, 2027 for state or local governments with a population of 50,000 or more
- April 26, 2028 for state or local governments with a population under 50,000
- April 26, 2028 for special district governments

The rule is specific to state and local governments under ADA Title II. It should not be presented as the rule for every private company. Its limited exceptions also do not eliminate broader duties involving effective communication, reasonable modifications, and equal access.
The Revised Section 508 Standards apply to federal agencies and certain federal procurement contexts. Current Section508.gov guidance explains that federal ICT accessibility reporting uses the applicable Revised Section 508 requirements, which incorporate WCAG 2.0 Level A and AA criteria.
This article provides technical and operational guidance, not a legal determination. Verify the laws, contracts, policies, sector requirements, and procurement rules that apply to your organization with qualified accessibility and legal professionals.
Use ATAG for the article editor and administration interface
The Authoring Tool Accessibility Guidelines address two connected responsibilities:
- Part A: Make the authoring tool itself accessible so disabled people can create and manage content.
- Part B: Help authors produce accessible content through appropriate controls, prompts, checks, templates, and guidance.

ATAG 2.0 references WCAG 2.0 because that was the current WCAG version when ATAG was published. W3C currently encourages using the latest WCAG 2 version when evaluating authoring-tool interfaces and generated content.
The Five Layers of Knowledge Base Accessibility
The following model is an adaptable operating framework, not a universal standard. A small help center may combine several layers, while an enterprise platform may assign different owners, systems, and testing processes to each one.
| Layer | What it includes | Typical accessibility risks |
|---|---|---|
| 1. Knowledge content | Article text, headings, lists, links, images, video, tables, code, and files | Missing structure, vague links, inaccessible media, image-only instructions, and complex files |
| 2. Reader interface | Homepage, search, navigation, results, article template, feedback, forms, and authentication | Keyboard barriers, poor focus behavior, missing labels, inaccessible search updates, and weak recovery states |
| 3. Authoring and administration | Editor, media manager, taxonomy, workflows, analytics, settings, and theme tools | Inaccessible menus, drag-only tasks, unlabeled controls, timeouts, and inaccessible dashboards |
| 4. Delivery channels | Public help center, internal portal, mobile app, in-app widget, chatbot, agent workspace, and APIs | Inconsistent behavior, inaccessible dialogs, permission leakage, poor mobile support, and third-party failures |
| 5. Operations and governance | Standards, procurement, testing, remediation, training, ownership, releases, and reporting | One-time audits, unclear ownership, stale ACRs, untested changes, and unresolved user reports |
A failure in one layer can make the entire experience inaccessible. For example, an accessible article cannot be reached if search suggestions are keyboard-inoperable. An accessible help-center theme does not help a disabled author who cannot use the article editor. An accessible widget does not fix a PDF that lacks tags and reading order.
Map the Complete Accessible User Journey
Do not assume that every person begins on the knowledge-base homepage or uses a mouse. Users may arrive from a search engine, product error, direct link, email, intranet, chatbot, mobile application, or support form.
| Journey stage | Potential barrier | Accessible design response | How to test it |
|---|---|---|---|
| Enter the knowledge base | Unclear page purpose, missing language, inaccessible product navigation | Descriptive page title, page language, recognizable heading, and accessible entry links | Direct-link, external-search, mobile, keyboard, and screen-reader tests |
| Search or browse | Unlabeled search, mouse-only menu, vague categories | Programmatic labels, keyboard operation, meaningful task-based navigation | Keyboard, speech-input, screen-reader, and comprehension tests |
| Use suggestions or filters | Focus trap, silent updates, inaccessible custom controls | Documented combobox behavior, status announcements, and native controls where practical | Keyboard and assistive-technology interaction tests |
| Evaluate results | Duplicate titles, missing context, hidden restricted content | Specific titles, useful excerpts, scope information, and enforced permissions | Representative-query and unauthorized-user tests |
| Read an article | Weak headings, long blocks, poor contrast, incorrect reading order | Semantic structure, plain language, responsive layout, and clear task flow | Heading navigation, zoom, reflow, reading-order, and comprehension tests |
| Complete the task | Image-only instructions, inaccessible forms, unclear expected result | Complete text steps, labeled controls, specific errors, and a verification step | End-to-end task completion using different input methods |
| Recover from failure | Dead-end no-results page, inaccessible 404, unexplained denied access | Preserved context, clear next action, alternate route, and safe support escalation | Error-state, expired-session, permission, and service-outage tests |
| Reach human help | Help changes location, inaccessible chat, repeated data entry | Consistent help placement, accessible contact options, and permitted context handoff | Keyboard, screen-reader, cognitive, and handoff testing |
Page Structure, Landmarks, and Orientation
Every important knowledge page should remain understandable when opened directly. A user should be able to identify the page, determine whether it applies, understand its place in the content structure, and find the next action without first visiting the homepage.
Provide meaningful document structure
- Use a unique and descriptive page title.
- Declare the primary page language and identify meaningful language changes.
- Use one logical page-level heading.
- Use heading levels to communicate hierarchy rather than visual size.
- Use real lists instead of manually typed bullets, dashes, or numbers.
- Use a main landmark for the primary article content.
- Label repeated navigation landmarks when their purposes differ.
- Provide a working skip link for repeated page regions.
- Use a table of contents for long articles when it improves navigation.
- Ensure sticky headers do not cover headings or focused controls.
The W3C writing guidance explains that semantic headings help readers understand the article outline and let assistive-technology users navigate between sections. Making text larger or bolder does not create a programmatic heading.
Use breadcrumbs as one orientation aid, not the only path
Breadcrumbs can show hierarchy and help users move to broader topics. The W3C breadcrumb pattern recommends placing the trail inside a labeled navigation landmark and identifying the current page appropriately.
Breadcrumbs do not replace search, local navigation, related tasks, or a clear article title. They can also become difficult to use on narrow screens if labels are long or densely packed.
Accessible Search, Suggestions, Results, and No-Results States
Search is a complete interaction, not only an input field. Evaluate query entry, suggestions, loading, results, filters, no-results behavior, permissions, status messages, errors, and mobile use.
Make the search input understandable and operable
- Provide a visible or programmatically associated label.
- Do not use placeholder text as the only label.
- Give an icon-only submit button an accessible name.
- Support keyboard submission and normal text editing.
- Keep the query visible and editable on the results page.
- Explain the search scope when several products, languages, or audiences are available.
- Preserve appropriate search state during Back and Forward navigation.
- Make loading and unavailable states understandable.
- Test at high zoom and on narrow mobile screens.
- Review the privacy implications of collecting and storing search terms.
The U.S. Web Design System search guidance recommends a programmatic label, a functional submit control, a full search field on important entry pages, and retention of the original query on results pages.
Implement autocomplete as an interactive component
Search suggestions require deliberate accessible-name, role, state, focus, and keyboard behavior. The current W3C combobox pattern provides implementation guidance for inputs with associated suggestion popups.
- Define when the suggestion list opens and closes.
- Support expected Down Arrow, Up Arrow, Enter, Escape, and text-editing behavior.
- Make the active suggestion available to assistive technology.
- Do not trap focus inside the suggestion list.
- Do not expose unauthorized article titles as suggestions.
- Communicate loading and no-suggestion states without excessive announcements.
- Test with supported browser and screen-reader combinations.
- Test mobile keyboards, touch behavior, and narrow screens.

Adding ARIA attributes does not make an autocomplete accessible when the keyboard behavior, focus model, visual state, and generated suggestions do not match the intended pattern.
Structure search results for efficient evaluation
- Use a specific result title.
- Provide an excerpt that explains why the result may be relevant.
- Include product, version, audience, language, or category only when it changes the decision.
- Use headings and lists so results can be navigated programmatically.
- Keep focus order consistent with the visual order.
- Avoid several adjacent links to the same destination.
- Make filters operable with keyboard, touch, and assistive technology.
- Preserve the query and filter state where practical.
- Use an accessible pagination or progressive-loading pattern.
- Ensure unauthorized users cannot receive restricted titles, excerpts, attachments, or metadata.
Announce dynamic search status without moving focus unnecessarily
Brief messages such as “Searching,” “18 results returned,” and “No results returned” may be status messages when the page updates without a full reload. The W3C status-message guidance explains that these changes should be programmatically available to assistive technology without unnecessarily moving focus.
Do not announce every character typed or every incremental result update in a way that overwhelms the user. Match announcement timing and priority to the importance of the information.
Turn no results into a recovery path
- State clearly that no matching result was found.
- Preserve the original query.
- Offer spelling corrections or alternative terminology.
- Suggest nearby categories when they are genuinely relevant.
- Allow an immediate revised search.
- Provide an accessible missing-topic report.
- Offer a human support route.
- Log the failed query for content and search review.
- Avoid blaming the user or replacing the answer with promotional content.
A zero-result query does not always require a new article. The better response may be a synonym, title change, metadata fix, permission correction, navigation change, product improvement, or personalized support route.
Navigation and Consistent Help
Search and browsing serve different user needs. A person with a precise error code may search, while a new user may browse by task or product. An article reached from an external search engine may need local navigation and related tasks to provide context.
- Keep global and local navigation labels consistent.
- Use task-oriented language rather than internal department names.
- Show the current page or active section.
- Make menus keyboard operable and screen-reader understandable.
- Provide a back-to-results route that preserves the query and filters.
- Use related articles for genuine prerequisites or next tasks.
- Make language and version selectors accessible.
- Test browser Back behavior and deep links.
- Avoid hiding essential navigation behind unlabeled icons.
WCAG 2.2 includes Consistent Help. When specified help mechanisms are repeated across a set of pages, they must occur in the same relative order unless the user initiates a change in layout. The criterion does not require every page to provide help, but it requires repeated help to remain predictably located.
Keyboard Operation and Focus Management
All knowledge-base functionality must be usable without a mouse where the interface relies on keyboard-operable web controls. Testing should cover the complete task rather than confirming that focus can reach the first link.
Keyboard-test the full interface
- Skip link
- Header and mobile navigation
- Search input and submit button
- Autocomplete suggestions
- Filters and sorting
- Result links and pagination
- Article table of contents
- Disclosures and accordions
- Copy buttons and code controls
- Feedback controls
- Forms and file uploads
- Authentication
- Chat launchers and support widgets
- Dialogs, drawers, and modals
- Downloads and external links
Keep focus visible and unobscured
A visible focus indicator helps sighted keyboard and switch users understand the current interaction point. The WCAG 2.2 Focus Not Obscured guidance requires a focused component to remain at least partially visible rather than being completely hidden by author-created content.
- Test sticky headers and footers.
- Test cookie banners.
- Test survey and chat widgets.
- Test support launchers fixed to screen corners.
- Test zoomed and narrow layouts.
- Test focus after validation errors.
- Test focus after a dialog or drawer closes.
Do not repair a poor document order with positive tabindex values. Correct the source and interaction order instead.
Manage modal, drawer, and widget focus deliberately
When a modal help viewer opens, move focus to a logical element inside it, contain focus when the interaction is truly modal, provide a clear close control, support Escape where appropriate, and return focus to the invoking control. Use the current W3C modal dialog pattern as implementation guidance.
A drawer or panel is not automatically modal. Match the focus behavior to the actual interaction and test it with assistive technologies.
Visual Presentation, Zoom, Reflow, and Mobile Use
A responsive layout is not proof of accessibility. Test how the knowledge base behaves when text is enlarged, browser zoom is increased, spacing is overridden, the screen is narrow, or the user applies high-contrast and other display settings.
Test more than text contrast
- Text contrast
- Link identification
- Focus indicators
- Input and button boundaries
- Error and selected states
- Icons that convey meaning
- Chart and diagram elements
- Disabled and hover states
- Dark mode
- Forced-colors and high-contrast modes
The W3C Non-text Contrast guidance explains that visual information needed to identify interface components and important graphical objects generally requires sufficient contrast against adjacent colors.
Do not rely on color alone for required fields, errors, status, selected filters, code syntax, or chart categories. Add text, patterns, shapes, labels, or other programmatically available cues.
Support zoom and reflow
The W3C Reflow guidance addresses the need for most reading content to remain usable without two-dimensional scrolling at narrow widths or high zoom, with limited exceptions for content such as complex data tables and diagrams that genuinely require two-dimensional layout.

- Ensure article text reflows rather than disappearing or being clipped.
- Allow long URLs and code strings to wrap or scroll appropriately.
- Place necessary wide tables in clearly usable scroll containers.
- Keep search, navigation, and support controls usable at narrow widths.
- Prevent sticky elements from consuming most of the viewport.
- Do not disable browser or mobile zoom.
- Test enlarged text and user-defined text spacing.
Provide usable touch targets
WCAG 2.2 Target Size (Minimum) requires applicable pointer targets to be at least 24 by 24 CSS pixels or to meet an allowed exception such as sufficient spacing. The criterion includes exceptions for inline links and certain equivalent or user-agent-controlled targets. Review the complete Target Size guidance rather than applying the number without context.
Pay particular attention to closely packed category links, article feedback buttons, filter chips, copy controls, pagination, mobile menu controls, and help launchers.
Cognitive Accessibility and Plain Language
WCAG does not capture every cognitive and learning need. Go beyond minimum technical conformance when clearer language, predictable interaction, and reduced memory demand improve the task.
- Put the direct answer near the beginning.
- Use short, concrete sentences.
- Define unfamiliar terms and expand acronyms.
- Use consistent labels across the product and knowledge base.
- Break complex procedures into manageable steps.
- State prerequisites before the actions.
- State the expected result after the actions.
- Keep warnings near the action they constrain.
- Avoid unnecessary time limits.
- Avoid requiring users to remember information from another page.
- Preserve entered information after recoverable errors.
- Make error messages specific and actionable.
- Do not use jokes, blame, or ambiguous language in failure states.
- Provide a human support route.
WCAG 2.2 Accessible Authentication addresses authentication tasks that impose unnecessary cognitive-function tests. The W3C guidance identifies password-manager support and copy-and-paste as mechanisms that can reduce memory and transcription burdens.
Accessible Knowledge Article Design
An accessible article helps readers determine quickly whether it applies, understand what to do, verify the result, and recover when the instructions do not work.
| Article element | Accessibility purpose |
|---|---|
| Task-based title | Explains the article’s purpose and distinguishes it from similar results |
| Audience and scope | Clarifies product, plan, version, role, region, or other applicability conditions |
| Direct answer | Reduces unnecessary reading and cognitive load |
| Prerequisites | Prevents users from beginning a procedure they cannot complete |
| Semantic steps | Communicates sequence and supports structured navigation |
| Expected result | Lets users verify whether the task succeeded |
| Exceptions and limitations | Prevents an apparently simple answer from becoming misleading |
| Troubleshooting and recovery | Provides an accessible response when the primary path fails |
| Support escalation | Prevents self-service from becoming a barrier to assistance |
Use meaningful headings, links, and lists
- Use headings that describe the section rather than generic labels such as “Overview” or “More.”
- Use descriptive link text that makes sense outside the surrounding sentence.
- Identify downloadable file type and size when that information affects the decision.
- Use numbered lists for genuine sequences.
- Use bulleted lists for collections whose order does not matter.
- Do not type visual bullets or numbers manually.
- Do not use tables for page layout.
The W3C writing tips recommend descriptive page titles, semantic headings, meaningful link text, clear instructions, text alternatives, captions, and transcripts.
Avoid visual-only instructions
Instructions such as “select the green button on the right” depend on color and spatial position. Use the visible and accessible control name instead, such as “Select Save changes.”
Do not make screenshots the only source of interface labels or procedural steps. Interfaces change, text inside images does not reflow well, and screen readers cannot derive complete instructions from a screenshot.
Images, Screenshots, Audio, Video, Tables, and Code
Choose alternative text according to the image’s purpose
Not every image needs descriptive alternative text. Use the W3C alt decision tree to classify the image according to its function and context.

| Image type | Typical treatment |
|---|---|
| Informative image | Provide concise alternative text conveying the relevant meaning |
| Functional image | Describe the action or destination rather than the image’s appearance |
| Decorative image | Use an empty alternative so assistive technology can ignore it |
| Redundant image | Use an empty alternative when the same information is already conveyed in nearby text |
| Complex chart or diagram | Provide a short identification plus a longer text explanation or data equivalent |
| Image of text | Prefer real text; when unavoidable, ensure the text alternative conveys the necessary content |
For complex images, the W3C complex-images guidance recommends a short description plus a longer textual representation of the essential information. State the main conclusion in the surrounding article rather than requiring every reader to interpret the graphic.
Make screenshots supplemental
- Provide complete instructions in text.
- Crop to the relevant region without removing necessary orientation.
- Remove names, email addresses, credentials, and other sensitive information.
- Identify the product or interface version when important.
- Use alternative text that explains the screenshot’s role in the article.
- Review the screenshot after material interface changes.
- Avoid relying only on colored arrows or outlines.
Provide accessible audio and video alternatives
The W3C audio and video guidance addresses captions, transcripts, visual description, accessible media players, and planning accessibility before production.
- Provide accurate captions for meaningful speech and sounds.
- Provide a transcript for audio information.
- Provide description of important visual information when required.
- Use a keyboard-accessible media player with labeled controls.
- Do not autoplay unexpected audio.
- Provide pause, stop, volume, and full-screen controls where applicable.
- Respect reduced-motion preferences.
- Do not force users to watch a long video to obtain one essential instruction.
Use semantic data tables
The W3C tables tutorial explains that accessible data tables require programmatic relationships between header and data cells.
- Use tables only for data relationships, not visual layout.
- Use
<th>for header cells and<td>for data cells. - Use
scope="col"andscope="row"for simple directional relationships where appropriate. - Use more explicit header associations for genuinely complex tables.
- Provide a caption when it helps readers identify the table.
- Provide orientation information for complex structures.
- Test screen-reader navigation and narrow-screen behavior.
- Consider an alternative presentation when the table cannot remain usable on mobile.
Make code examples selectable and operable
- Provide code as text rather than a screenshot.
- Identify the language or purpose.
- Do not rely on syntax color alone.
- Allow long lines to wrap or scroll without hiding content.
- Give copy buttons an accessible name.
- Announce successful copying without unexpectedly moving focus.
- Provide error examples and expected output in text.
Accessible PDFs and Downloadable Documents
A downloadable file is part of the knowledge experience. The article page does not become accessible merely because the surrounding HTML is usable.
Where practical, provide essential guidance as responsive HTML. Current Section508.gov PDF guidance notes that PDFs are often less accessible and less mobile-friendly than HTML and recommends prioritizing digital-first formats in federal contexts.
Evaluate each file format deliberately
- Document title and filename
- Declared language and language changes
- Heading and list structure
- Reading order
- Table structure
- Alternative text
- Link purpose
- Form-field labels and instructions
- Color and contrast
- Captions and transcripts
- Tags and bookmarks where appropriate
- File type, size, version, and effective date
- Accessibility test results
- Remediation owner
Section508.gov provides separate current resources for word-processing documents, PDFs, spreadsheets, and presentations.
Do not assume that converting a Word document to PDF makes it accessible. Scanned, image-only, poorly tagged, or incorrectly ordered files may require significant remediation.
Forms, Errors, Authentication, and Restricted Content
Design accessible feedback and support forms
- Use visible, programmatically associated labels.
- Identify required fields in text and markup.
- Provide format instructions before submission.
- Group related controls with appropriate structure.
- Identify errors specifically and connect them to affected fields.
- Provide an error summary for longer forms when useful.
- Preserve valid user input after an error.
- Announce submission status and confirmation appropriately.
- Provide an alternative to inaccessible CAPTCHA.
- Review timeouts and allow extensions where appropriate.
- Make file uploads keyboard and assistive-technology usable.
The W3C forms tutorial covers labels, grouping, instructions, validation, notifications, multi-step forms, and custom controls.
Support accessible authentication
- Allow password managers.
- Allow appropriate copy and paste.
- Provide an accessible alternative to cognitive puzzles.
- Make one-time-code workflows understandable and operable.
- Make multi-factor options accessible across supported devices.
- Provide accessible account recovery.
- Preserve the requested destination after sign-in where safe.
- Explain session expiration and the next action.
Protect restricted knowledge without leaking metadata
Authentication proves identity; authorization determines access. Personalization and targeting do not grant permission.
Unauthorized users must not receive protected:
- Article titles
- Search suggestions
- Result snippets
- Category names or counts
- Attachments
- Related links
- API responses
- AI citations or generated summaries
Design denied-access states to explain a valid next step—such as signing in or requesting access—without revealing the protected subject or content.
Authoring-Tool and Administration Accessibility
A complete evaluation includes authors, reviewers, translators, knowledge managers, and administrators with disabilities.
Test whether disabled authors can complete real tasks
- Create and title an article.
- Apply semantic headings and lists.
- Add an image and alternative text.
- Mark a decorative image correctly.
- Create an accessible table.
- Add captions or transcripts.
- Insert descriptive links.
- Apply taxonomy and metadata.
- Submit the article for review.
- Review comments and make changes.
- Approve, publish, schedule, or retire content.
- Use analytics and accessibility reports.
- Manage theme and administrative settings.
Evaluate how the tool supports accessible content creation
- Semantic heading controls
- Real list controls
- Accessible-table support
- Alternative-text fields
- Decorative-image handling
- Caption and transcript fields
- Language metadata
- Descriptive-link guidance
- Accessible templates
- Contrast and structure warnings
- Preview across responsive layouts
- Accessibility checks integrated into authoring
- Reporting for inaccessible or incomplete content
An automated checker inside the editor can help authors catch some issues, but it cannot determine whether alternative text communicates the correct purpose, whether a procedure is understandable, or whether every interactive workflow is usable.
For example, current ServiceNow documentation describes an article-editor accessibility checker that identifies certain issues and offers suggestions. Such a feature is useful evidence, but it is not a substitute for complete manual evaluation.
Mobile, Embedded, In-App, and AI Delivery
Test the actual in-app surface
An accessibility statement for the standalone help center does not prove that an embedded widget, mobile SDK, modal viewer, side panel, iframe, or custom API-rendered interface is accessible.
- Give the launcher an accessible name.
- Make it keyboard and touch operable.
- Keep its focus indicator visible.
- Place focus appropriately when the panel opens.
- Provide predictable close and focus-return behavior.
- Use semantic headings inside the panel.
- Label in-panel search and forms.
- Test zoom, reflow, orientation, and mobile screen readers.
- Do not let the launcher obscure other focused controls.
- Keep the product’s primary workflow usable if the widget fails.
Make chatbot and AI answers accessible
- Give the chat input a clear label.
- Structure messages so they can be navigated and understood.
- Announce new content without reading every streaming token as a separate interruption.
- Provide a stop-generation control.
- Make citations descriptive, keyboard operable, and permission aware.
- Give copy and feedback controls accessible names.
- Preserve important conditions and exceptions from source content.
- Provide no-answer and clarification behavior.
- Provide an accessible route to a human.
- Make the conversation transcript available where appropriate.
An accessible chat interface does not prove the generated answer is correct. A citation does not prove that the right source was selected or interpreted properly. AI answers must respect permissions and should not silently replace approved policy with general model knowledge.
Custom Themes, Plugins, Localization, and Third-Party Components
Retest after customization
Built-in accessibility can be lost through custom templates, CSS, JavaScript, plugins, widgets, and integrations. Current Zendesk help-center guidance, for example, explains that customers who create custom themes take responsibility for their custom accessibility behavior and do not automatically receive all future theme improvements.
Evaluate:
- Theme forks and template changes
- Chat and survey widgets
- Cookie banners
- Video and code viewers
- Authentication providers
- Translation widgets
- Search extensions
- Analytics scripts
- Iframes and embedded forms
- Accessibility overlays
An accessibility overlay does not remove the need to fix underlying content, code, interaction, authoring, and process barriers.
Treat localization as an accessibility workflow
- Declare the page language.
- Identify language changes inside an article.
- Translate navigation, forms, errors, alternative text, captions, and support routes.
- Test right-to-left directionality where applicable.
- Plan for text expansion.
- Verify font and character support.
- Test search and suggestions in each language.
- Provide locale-appropriate formats.
- Track translation freshness and source changes.
- Review machine translation before publishing consequential content.
How to Test Knowledge Base Accessibility
No single tool or test method is sufficient. Automated checks, manual inspection, keyboard testing, assistive-technology testing, content review, and testing with disabled people answer different questions.
Use the current WCAG-EM evaluation process
WCAG Evaluation Methodology 2.0, published in July 2026, provides a five-step process:
- Define the evaluation scope.
- Explore the target digital product.
- Select a representative sample set.
- Evaluate the selected sample.
- Report the findings.

The methodology is designed for evaluating a representative digital product rather than checking one convenient page and generalizing the result to the entire system.
Select a representative knowledge-base sample
| Sample type | Why it belongs in the evaluation |
|---|---|
| Homepage | Tests orientation, search, categories, global navigation, and help access |
| Search suggestions | Tests custom-control behavior, focus, announcements, and permission enforcement |
| Search results | Tests status updates, headings, filters, result context, and keyboard order |
| No-results state | Tests recovery, preserved query, support access, and cognitive clarity |
| Standard article | Tests the normal article template and common content structure |
| Long article | Tests headings, table of contents, sticky controls, and deep linking |
| Table- or code-heavy article | Tests complex reading and responsive behavior |
| Media article | Tests captions, transcript, player controls, and visual description |
| Feedback or contact form | Tests labels, errors, confirmation, and support handoff |
| Login and restricted content | Tests accessible authentication, denied states, and permission leakage |
| 404, retired, or moved page | Tests error recovery and replacement guidance |
| Mobile and in-app view | Tests the actual narrow-screen or embedded delivery surface |
| Authoring interface | Tests whether disabled authors can create, review, and publish accessible content |
| Downloadable document | Tests the accessibility of files delivered through the knowledge base |
| AI or chatbot experience | Tests announcements, navigation, citations, permissions, and human handoff |
Combine complementary testing methods
| Method | What it can reveal | What it cannot establish alone |
|---|---|---|
| Automated scan | Some missing names, invalid relationships, contrast issues, missing attributes, and structural defects | Complete accessibility, correct alternative text, understandable instructions, or usable workflows |
| Keyboard test | Focus order, traps, operability, visible focus, and focus obscuring | Screen-reader meaning, visual contrast, or cognitive clarity |
| Zoom and reflow test | Clipping, overlap, missing content, sticky-element problems, and horizontal scrolling | All keyboard, screen-reader, or content issues |
| Screen-reader test | Names, roles, states, landmarks, headings, reading order, and dynamic announcements | Every visual, motor, cognitive, or mobile barrier |
| Content review | Plain language, structure, descriptive links, media alternatives, and procedural completeness | Actual interactive behavior |
| Testing with disabled people | Real task barriers, strategies, context, and usability issues missed by technical reviews | Automatic proof of full conformance across the entire system |
W3C’s evaluation-tool guidance states that tools cannot check every accessibility aspect automatically and that human judgment is required.
Report and Prioritize Accessibility Defects
An actionable accessibility finding should contain enough detail to reproduce, understand, fix, assign, and retest the problem.
- Stable issue ID
- Affected page, template, component, or file
- User task
- Disability-related impact
- Applicable success criterion or requirement
- Severity and frequency
- Reproduction steps
- Browser, device, and assistive technology
- Evidence
- Recommended correction
- Owner and target date
- Status
- Retest result
- Regression-test opportunity
Prioritize shared and task-blocking defects first
- Barriers preventing completion of essential tasks
- Authentication and restricted-content barriers
- Shared template and component defects affecting many pages
- Search and navigation barriers
- High-risk forms, policies, and documents
- Repeated authoring defects
- Lower-impact enhancements
Fixing a shared search component, article template, or authoring control often removes more barriers than repairing the same defect independently on many articles.
Do not use an automated accessibility score as the sole priority method. A lower-frequency login blocker may be more severe than hundreds of easily detected cosmetic warnings.
Evaluate Accessible Knowledge Base Software
Procurement should evaluate the specific product version, plan, interfaces, integrations, and configuration the organization intends to deploy. A general corporate accessibility statement is not enough.
Request current, scoped accessibility evidence
- Current Accessibility Conformance Report
- VPAT edition used
- Product version and plan covered
- Report date
- Reader-facing interface scope
- Authoring and administration scope
- Mobile application scope
- In-app widget or embedded-help scope
- AI and chatbot scope
- Exported files and support-documentation scope
- Testing methodology
- Automated and manual testing performed
- Browsers and assistive technologies tested
- Known issues and workarounds
- Remediation roadmap
- Accessibility contact
- Release-regression process
- Customer issue-reporting process
- Custom-theme and third-party responsibilities
Section508.gov distinguishes the ACR from the VPAT template and recommends reviewing accessibility evidence rather than accepting a vendor claim without validation. Its vendor-information guidance also recommends demonstrations, remediation plans, testing information, and accessible-content samples where authoring tools are involved.

Read every “Partially Supports” explanation
An ACR may identify that a requirement is supported, partially supported, not supported, or not applicable. Review the remarks for:
- The exact affected component
- The user impact
- The conditions under which the defect occurs
- Available workaround
- Whether the workaround is practical
- Expected remediation date
- Whether customization changes the result
An old ACR may no longer describe the current product. Section508.gov notes that product changes and version changes can require an updated report.
Run buyer-defined accessibility scenarios
- Find an article through keyboard-only search.
- Operate autocomplete with a screen reader.
- Use filters and return to the results page.
- Read a long article at high zoom.
- Complete a support form and recover from errors.
- Sign in using a password manager and multi-factor authentication.
- Confirm that an unauthorized user cannot discover restricted content.
- Create an article using a screen reader.
- Add an accessible image and table through the editor.
- Review and approve the article without a mouse.
- Use the mobile application or in-app widget.
- Read and verify an AI answer and its citations.
Document the required outcome before the demonstration or trial. Do not accept a prerecorded marketing demonstration as proof of the configured production workflow.
Governance and Implementation Roadmap
Knowledge Base Accessibility is an ongoing operating responsibility. New articles, product releases, theme changes, integrations, translations, and AI features can introduce new barriers after an initial audit.
Assign distributed responsibility
| Role | Typical responsibility |
|---|---|
| Accessibility program owner | Standards, policy, reporting, escalation, and program coordination |
| Knowledge manager | Templates, article standards, ownership, lifecycle, and content audits |
| Product and UX teams | Reader interface, search, navigation, component behavior, and design system |
| Engineering | Semantic implementation, keyboard interaction, focus, integrations, and regression fixes |
| Writers and content designers | Structure, plain language, links, text alternatives, media, and procedural completeness |
| Platform administrators | Themes, permissions, authentication, plugins, settings, and release controls |
| Procurement and vendor management | Accessibility evidence, contract requirements, demonstrations, and remediation commitments |
| Quality and testing teams | Automated, manual, assistive-technology, mobile, and regression testing |
| Support Operations | User reports, accessible escalation, issue routing, and recurring barrier analysis |
| Legal and compliance | Applicable legal, contractual, policy, and procurement requirements |
Use an adaptable implementation sequence
- Define audiences and essential tasks. Include readers, authors, reviewers, administrators, and support users.
- Identify applicable requirements. Document the WCAG target, laws, contracts, procurement terms, and internal policy.
- Define scope. Include websites, mobile apps, widgets, AI, authoring tools, documents, and third parties.
- Inventory templates and states. Include search, results, articles, forms, authentication, errors, and restricted content.
- Review vendor evidence. Check the product version, interfaces, ACR scope, known limitations, and responsibilities.
- Select representative journeys. Use real tasks rather than isolated pages.
- Establish a baseline. Combine automation, keyboard, zoom, reflow, screen-reader, mobile, and content testing.
- Include disabled users. Test with people whose lived experience is relevant to the identified tasks.
- Prioritize shared blockers. Fix templates and components before repeating the same article-level repair.
- Improve the authoring system. Add accessible templates, controls, checks, and guidance.
- Remediate priority content and files. Start with frequently used and high-risk knowledge.
- Add regression tests. Protect search, navigation, forms, authentication, and article templates.
- Train responsible roles. Tailor training to writers, designers, developers, administrators, buyers, and reviewers.
- Publish an issue-reporting route. Make it accessible and ensure reports reach an accountable owner.
- Retest production. Verify the deployed configuration, not only staging or vendor documentation.
- Monitor changes. Retest after major releases, theme updates, plugins, connectors, and AI changes.
Use operational metrics carefully
- Open blockers by user journey
- Time to remediate
- Regression rate
- Templates and components tested
- Representative journeys tested
- Articles and files sampled
- Media with reviewed captions and transcripts
- Authors and administrators trained
- Vendor reports reviewed
- Accessibility-related support requests
- Keyboard-task and screen-reader-task success
- Zoom and reflow defects
- Authentication failures
- Restricted-content leakage incidents
Zero reported complaints do not prove that no barriers exist. A completed audit does not prove ongoing accessibility. A passing template does not prove that every article created with it is accessible.
Knowledge Base Accessibility Checklist
Standards and scope
- The applicable WCAG target is documented.
- Legal, contractual, and procurement requirements are distinguished from W3C recommendations.
- The evaluation covers reader, author, administrator, mobile, embedded, file, and AI experiences as applicable.
- Custom themes and third-party components are included.
Structure and navigation
- Pages have descriptive titles and correct language metadata.
- Headings communicate hierarchy.
- Landmarks and navigation regions are meaningful.
- A skip link works.
- Breadcrumbs and tables of contents are usable.
- Repeated help appears consistently.
Search and results
- The search input has a programmatic label.
- Autocomplete is keyboard and screen-reader operable.
- Dynamic search status is announced appropriately.
- Results have specific titles and useful context.
- No-results states preserve the query and provide recovery.
- Restricted metadata is not exposed.
Keyboard, focus, and interaction
- All functionality is keyboard operable.
- Focus order follows the intended task.
- Focus indicators are visible.
- Sticky elements do not hide focused components.
- Dialogs and drawers manage focus correctly.
- There are no keyboard traps.
- Touch targets are appropriately sized or spaced.
Content and media
- Articles use plain language and complete instructions.
- Links are descriptive.
- Lists and tables use semantic markup.
- Images have context-appropriate alternatives.
- Complex images have extended text equivalents.
- Videos have reviewed captions and appropriate transcripts or descriptions.
- Code is available as text.
- Downloads are evaluated or accompanied by an accessible equivalent.
Visual and mobile behavior
- Text and essential graphics have sufficient contrast.
- Color is not the only indicator.
- Text can be enlarged without clipping.
- Content reflows at narrow widths.
- Wide tables and code remain usable.
- Zoom is not disabled.
- Mobile navigation, search, forms, and Back behavior work.
Forms, authentication, and support
- Forms use labels, instructions, and specific errors.
- Valid input is preserved after errors.
- Password managers and appropriate paste behavior are supported.
- Multi-factor and account-recovery workflows are accessible.
- Denied-access states do not reveal protected content.
- A consistent, accessible human-support route exists.
Authoring, testing, and governance
- Disabled authors can create, review, approve, and publish content.
- The editor supports semantic accessible content.
- Automated checks are combined with manual testing.
- A representative sample and complete tasks are tested.
- Defects have owners, severity, evidence, and retest results.
- Accessibility evidence is reviewed during procurement.
- Regression tests run after material changes.
- User reports reach an accountable team.
Sources Checked
- W3C WAI: WCAG 2 Overview
- W3C WAI: What’s New in WCAG 2.2
- W3C WAI: How to Meet WCAG 2.2
- W3C WAI: Authoring Tool Accessibility Guidelines
- W3C: WCAG Evaluation Methodology 2.0
- W3C WAI: Selecting Accessibility Evaluation Tools
- W3C WAI: Writing for Web Accessibility
- W3C WAI: Alt Decision Tree
- W3C WAI: Tables Tutorial
- W3C WAI: Making Audio and Video Media Accessible
- W3C WAI: Forms Tutorial
- W3C WAI: Combobox Pattern
- W3C WAI: Modal Dialog Pattern
- ADA.gov: Title II Web and Mobile Application Rule Guidance
- U.S. Department of Justice: 2026 Interim Final Rule Extending Title II Compliance Dates
- Section508.gov: ACR and VPAT Frequently Asked Questions
- Section508.gov: Request Accessibility Information from Vendors
- Section508.gov: Create Accessible Digital Products
- U.S. Web Design System: Search Component
- Zendesk: Making Your Help Center Accessible
- Zendesk: Creating Accessible Help Center Content
- ServiceNow: Knowledge Article Accessibility Checker
Standards, legal sources, and product accessibility documentation checked on November 20, 2026.



