Skip to Content

PHPKB Accessibility

Estimated Reading Time: 3 Minutes

PHPKB is a modern browser-based knowledge base software and help-authoring documentation tool used by software companies all over the world to create online user manuals, help files, knowledge bases, FAQs, tutorials and publish them instantly in their online documentation portal. PHPKB always tends to meet clients’ needs and that’s why our knowledge management software is highly accessible according to Section 508 and WCAG 2.1 AA requirements and guidelines.

WCAG Compliant Software

Let us know about Section 508, WCAG 2.1 AA, and how PHPKB is compliant with these web accessibility standards.

What is Section 508?

Section 508 is part of the Rehabilitation Act of 1973. The document requires Federal agencies to make their ICT such as technology, websites, and online training accessible for everyone. The main goal of Section 508 is to provide employees with disabilities an accessible environment, so they can do their work on the accessible computers, equipment in their offices, phones, and take online training or access the agency’s internal website to locate needed information.

What is WCAG 2.1?

WCAG stands for Web Content Accessibility Guidelines. It is a document of recommendations for making Web content more accessible. These guidelines help to make content accessible to a wider range of people with disabilities, including hearing and deafness loss, low vision and blindness, cognitive limitations, learning disabilities, limited movement, speech disabilities, etc. WCAG 2.1 is the stable, referenceable technical standard that’s organized under 4 principles: perceivable, operable, understandable, and robust. For the guideline, there are testable success criteria, which are at three levels: A, AA, and AAA. PHPKB follows the WCAG 2.1 Level AA standard.

What does Accessible Mean?

An information technology system can be considered accessible if it can be used in a variety of ways that don’t depend on a single ability or sense. For example, users should be able to navigate using not only a mouse but also a keyboard.

The guidelines of Section 508 and WCAG 2.1 can sound the same but there are some differences among both. For example, the guidelines of WCAG 2.1 say: “Ensure that equivalents for dynamic content are updated when the dynamic content changes”. However, this point is not included in Section 508.

How is PHPKB accessible?

PHPKB knowledge base software tends to provide better accessibility according to both standards - Section 508 and WCAG 2.1 Level AA. Here are some points:

  • To navigate through PHPKB easily, you can freely use screen readers since all non-text content (images, iframe, and object elements) that is presented to a user has a text alternative that serves the equivalent purpose.
  • A screen reader can also identify the code as ARIA attributes are added. It’s helpful when a user inserts a wrong password, so the alert role of the ARIA attribute will trigger the screen reader to warn a user about the error.
  • PHPKB doesn’t require speech, mobility, or auditory ability alone - people are able to use more than one mode of operation and information retrieval. For example, mobility-impaired people can use a mouse or keyboard depending on their needs.
  • HTML tables can be generated so that column and row headers can be identified by screen review aids.
  • Authors can use different colors in order to not rely on color alone to communicate information, selections, or errors.
PHPKB Accessibility