Skip to main content

Bestax Accessibility Conformance Report

International Edition

(Based on VPAT® Version 2.5Rev)

Name of Product/Version: @allxsmith/bestax-bulma 5.x, the release on npm at the report date, and the bestax.io site

Report Date: November 2026

Product Description: Bestax is a React component library for the Bulma CSS framework, published to npm as @allxsmith/bestax-bulma, and bestax.io is its documentation site, with live examples of the components.

Contact Information: Open an issue with the Accessibility Issue template, or ask on Discord.

Notes:

  • Scope. This report covers the components in @allxsmith/bestax-bulma, rendered the way their API pages and Storybook stories show them, and bestax.io: the docs, the blog and the live examples on their pages. An app built with Bestax isn't covered. WCAG conformance is defined for whole pages, so an app's conformance is its own, and the components can't settle the criteria that belong to a page, such as its title, its language or a way to skip its navigation. The accessibility statement lists what an app still owns.
  • Two parts per row. Each row's remarks give the components' part and the site's part, and its conformance level is the lower of the two.
  • Only Web applies. The template splits each WCAG row into Web, Electronic Docs, Software, Closed and Authoring Tool. Bestax is web content: a library that renders HTML in a browser, and a website. It ships no non-web documents, has no closed functionality, and isn't an authoring tool, since it has no editor and the content an app builds with it is the app's. So each row answers for Web, and Electronic Docs, Software, Closed and Authoring Tool are Not Applicable for every row.
  • Known gaps. Remarks cite the open issues behind the gaps they describe. The open issues with the accessibility label are the full, up-to-date list, including a few, such as development warnings, that no single criterion covers. A fix that would change what existing apps rely on waits for the next major version and carries the next-major label, and the remarks say so.
  • Self-assessed. The maintainer wrote this report. It hasn't been audited by a third party.
  • Kept current. A fix that closes or opens a known gap updates its rows, and the report date above, in the same change. The rows describe the code on main, which reaches npm with the next release.

Evaluation Methods Used:

  • axe-core 4.14, through Storybook's accessibility addon, on every story of every component, in Chromium, in the light and the dark scheme, on every pull request. A violation fails the pull request unless the story's exemption names the open issue that tracks it, or the reason axe is wrong there. axe's contrast rule is off for the stories until #2188 is settled.
  • axe-core 4.14 on every page of the built bestax.io site, in both color modes, including the live examples a page shows (one inside a closed tab or a closed <details> isn't checked), after each change reaches main, with the same rule for exemptions. The site's contrast check is exempted until #2215 is settled.
  • Unit tests (Vitest, in jsdom) for the components' keyboard interaction and ARIA roles, states and properties, and, for the components those settings change, how they draw in forced colors and with reduced motion.
  • A simulated screen reader (Guidepup Virtual Screen Reader) for what TreeView announces.
  • Accessibility audits of the components and the site, whose findings are the issues with the accessibility label.
  • Not done yet: tests with NVDA, JAWS, VoiceOver or TalkBack, in a real Windows contrast theme rather than Chromium's emulation of one, or in Firefox or Safari. Text resizing, text spacing and reflow are judged from the CSS (Bulma sizes text in rem and em) rather than tested on every component.

Applicable Standards/Guidelines​

This report covers the degree of conformance for the following accessibility standard/guidelines:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.0Level A (Yes)
Level AA (Yes)
Level AAA (No)
Web Content Accessibility Guidelines 2.1Level A (Yes)
Level AA (Yes)
Level AAA (No)
Web Content Accessibility Guidelines 2.2Level A (Yes)
Level AA (Yes)
Level AAA (No)
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018(Yes)
EN 301 549 Accessibility requirements for ICT products and services, V3.1.1 (2019-11) and V3.2.1 (2021-03)(Yes)

Terms​

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: Some functionality of the product does not meet the criterion.
  • Does Not Support: The majority of product functionality does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.
  • Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

WCAG 2.x Report​

Tables 1 and 2 also document conformance with:

  • EN 301 549: Clause 9 (Web), Clauses 10.1 to 10.4 (Non-web documents), Clauses 11.1 to 11.4 and 11.8.2 (Software), and Clauses 12.1.2 and 12.2.4 (Documentation).
  • Revised Section 508: Chapter 5, 501.1 Scope and 504.2 Content Creation or Editing, and Chapter 6, 602.3 Electronic Support Documentation.

For Bestax only the web clauses among those apply: EN 301 549 Clause 9, 12.1.2 and 12.2.4, and Revised Section 508 501.1 and 602.3. The non-web document, software and authoring tool clauses are Not Applicable (see Notes). A criterion added in WCAG 2.1 also applies to EN 301 549, but not to the Revised Section 508 standards, which take in WCAG 2.0. A criterion added in WCAG 2.2 applies to neither. Each such row says so.

When reporting on conformance with the WCAG 2.x Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements.

Table 1: Success Criteria, Level A​

Notes: Electronic Docs, Software, Closed and Authoring Tool are Not Applicable throughout (see Notes, above), so each row answers for Web.

CriteriaConformance LevelRemarks and Explanations
1.1.1 Non-text Content (Level A)Web: Partially SupportsComponents: An Icon is decorative unless it's given an ariaLabel, and Image, Avatar and Card take the alternative text the app gives them. Card falls back to "Card image" for an image URL with no imageAlt, a placeholder rather than a description (#1750, next major). bestax.io: The site's images have text alternatives, which the axe pass checks on every page.
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Web: Not ApplicableComponents: No component plays audio or video. bestax.io: The site has no audio-only or video-only content.
1.2.2 Captions (Prerecorded) (Level A)Web: Partially SupportsComponents: No component plays media. bestax.io: The site's one video, a film embedded in the Image page's aspect-ratio example, has no captions (#2224).
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Web: Partially SupportsComponents: No component plays media. bestax.io: The same embedded film has no audio description or text alternative (#2224).
1.3.1 Info and Relationships (Level A)Web: Partially SupportsComponents: Components use native elements, ARIA patterns from the APG, and labels wired to their controls. Known gaps: the date grids leave a neighboring month's blank days out of the accessibility tree, so the days after them sit under the wrong weekday (#2194); Tabs.List calls a row of navigation links a tab list (#1917, next major); Modal's card head and foot carry page landmark roles (#2066, next major), as do Card's header and footer (#2199, next major); SubTitle renders a heading by default, and an explicit as loses to size for Title's and SubTitle's heading level (#1857, #1856, next major); a Button rendered as a link with isDisabled looks enabled (#1898), and so does a disabled Carousel arrow under the pointer with arrowHover (#2145); a popup opened inside a modal Sidebar, or inside a dialog when the app sets portalContainer, renders outside the modal, where a screen reader can't reach it (#1525, #1527, next major). bestax.io: The pages that show a Tabs.List carry its gap (#1917): the 2-to-3 migration guide and one blog post.
1.3.2 Meaningful Sequence (Level A)Web: Partially SupportsComponents: Components render their content in reading order, with one known exception: Rate's rtl prop reverses the order a screen reader meets the stars in, while they still show left to right (#1830, next major). The flex helpers' reversed directions change only the visual order, and the Flex guide says so. bestax.io: No known gaps.
1.3.3 Sensory Characteristics (Level A)Web: SupportsComponents: No component gives instructions by shape, size, position or sound alone. Instructions in an app are the app's. bestax.io: No known gaps.
1.4.1 Use of Color (Level A)Web: Partially SupportsComponents: A Link in running text differs from the text around it only by color (#1858), and a Timeline's completed and upcoming icon markers differ by color alone (#1991). bestax.io: Links in running text are marked by color alone (#2203).
1.4.2 Audio Control (Level A)Web: Not ApplicableComponents: No component plays audio. bestax.io: Nothing plays audio on its own; the embedded film plays only when started.
2.1.1 Keyboard (Level A)Web: Partially SupportsComponents: Interactive components follow the APG's keyboard patterns, and unit tests check them. Known gaps: the Combobox menu scrolls in a box the keyboard can't focus, which may be axe not seeing the combobox pattern (#2205); arrow keys don't swap direction on right-to-left pages in Tabs, SegmentedControl, the calendar, TimeWheels and Rate (#1336, next major). bestax.io: Wide tables on a few API pages scroll sideways, but the keyboard can't reach them (#2219).
2.1.2 No Keyboard Trap (Level A)Web: SupportsComponents: Modal, Sidebar and the other modal overlays keep focus inside while open, as the APG's dialog pattern does, and release it on close and on Escape. bestax.io: Tab and Shift+Tab move focus into and out of the live code examples' editor rather than indenting the code.
2.1.4 Character Key Shortcuts (Level A, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: Partially SupportsComponents: No component sets a single-key shortcut on its own. Command's optional shortcut is the app's choice of keys. bestax.io: The search opens on a bare / key, which can't be turned off (#2223).
2.2.1 Timing Adjustable (Level A)Web: Partially SupportsComponents: A plain Toast closes after two seconds by default (#2196, next major), a Toast with an action closes on a timer too (#1964, next major), and so does a programmatic notification, after three seconds (#2233, next major). An app can pass its own duration. bestax.io: Nothing on the site has a time limit.
2.2.2 Pause, Stop, Hide (Level A)Web: Partially SupportsComponents: Carousel's autoplay is off by default, but when it's on there's no control that stops it (#1925). bestax.io: The homepage's form-controls carousel plays on its own with no way to pause it (#2206).
2.3.1 Three Flashes or Below Threshold (Level A)Web: SupportsComponents: No component flashes. bestax.io: Nothing on the site flashes.
2.4.1 Bypass Blocks (Level A)Web: SupportsComponents: This is a page's criterion, the app's. AppFrame gives an app a skip link to its main region. bestax.io: Every page starts with a "Skip to main content" link.
2.4.2 Page Titled (Level A)Web: SupportsComponents: A page's criterion, the app's. bestax.io: Every page has a title naming it.
2.4.3 Focus Order (Level A)Web: Partially SupportsComponents: Overlays move focus in when they open and back to their trigger when they close. Dropdown's items are each a tab stop, where the APG's menu takes them out of the Tab order (#1477, next major). bestax.io: While the homepage's form-controls demo is on screen, it moves keyboard focus into its search input every few seconds (#2204).
2.4.4 Link Purpose (In Context) (Level A)Web: SupportsComponents: Link text is the app's. Pagination names its arrows "Previous" and "Next" unless the app passes its own. bestax.io: No known gaps.
2.5.1 Pointer Gestures (Level A, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: SupportsComponents: Nothing needs a multipoint or path-based gesture: Carousel's swipe has buttons and keys beside it. bestax.io: No known gaps.
2.5.2 Pointer Cancellation (Level A, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: SupportsComponents: Controls act on the click, when the pointer comes up, as native buttons do. bestax.io: No known gaps.
2.5.3 Label in Name (Level A, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: Partially SupportsComponents: The month picker shows "Jan" and names the cell "January" (#2209); a calendar day with content is named in a different order from what it shows (#2210); a clickable Avatar shows initials and is named in full (#2211). bestax.io: The search button's name doesn't contain the shortcut it shows (#2216).
2.5.4 Motion Actuation (Level A, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: Not ApplicableComponents: Nothing responds to device motion. bestax.io: Nothing responds to device motion.
3.1.1 Language of Page (Level A)Web: SupportsComponents: A page's criterion, the app's. bestax.io: Every page declares its language.
3.2.1 On Focus (Level A)Web: SupportsComponents: Taking focus changes no context. It can show a Tooltip or a HoverCard, or open a date or time picker's popover (openOnFocus, on by default), and none of those moves focus or changes the page. bestax.io: No known gaps.
3.2.2 On Input (Level A)Web: SupportsComponents: Changing a control's value changes no context unless the app does so in its handler. bestax.io: No known gaps.
3.2.6 Consistent Help (Level A, WCAG 2.2 only; Revised Section 508 and EN 301 549 do not apply)Web: SupportsComponents: A page's criterion, the app's. bestax.io: The ways to get help (GitHub and Discord) sit in the same place in the footer of every page.
3.3.1 Error Identification (Level A)Web: SupportsComponents: A form control's message shows the error the app writes and describes the control through aria-describedby, and the controls take aria-invalid. The error's words are the app's. bestax.io: The site has no forms beyond its search.
3.3.2 Labels or Instructions (Level A)Web: Partially SupportsComponents: A Field's label names the control it holds, and each control takes a name of its own. Known gaps: the date and time inputs put aria-label, aria-labelledby and aria-describedby on their wrapper rather than their field (#2025, next major), and Panel.InputBlock puts its field attributes on the div around its input (#1998, next major). bestax.io: Some live examples name a control only by aria-label or a placeholder, with no label on screen (#2252).
3.3.7 Redundant Entry (Level A, WCAG 2.2 only; Revised Section 508 and EN 301 549 do not apply)Web: SupportsComponents: A process's criterion, the app's. bestax.io: The site has no multi-step processes.
4.1.1 Parsing (Level A)Web: SupportsFor WCAG 2.0, 2.1, EN 301 549, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. WCAG 2.2 removed it as obsolete.
4.1.2 Name, Role, Value (Level A)Web: Partially SupportsComponents: Components expose their names, roles, states and values through native elements and ARIA. Known gaps, each waiting for the next major because it changes what a screen reader hears: Switch is announced as a checkbox (#1969); a non-editable Numberinput is a read-only field rather than a spin button (#1997); Message's close button is named "delete" (#1912); a static Button takes focus (#1872); a step's state isn't in its name (#1703); Carousel's indicators are a tab stop each and don't name the slides they control (#1924); the date pickers name their days by number alone (#1456); Carousel's and Navbar's default names include their role, which a screen reader then says twice (#1932, #1448); the glyph inside an unnamed Icon with a role of its own, a ligature's text or an SVG, can name it or the control around it, which a development build warns about (#2265). bestax.io: The live code examples' editor has no name (#2180).

Table 2: Success Criteria, Level AA​

Notes: Electronic Docs, Software, Closed and Authoring Tool are Not Applicable throughout (see Notes, above), so each row answers for Web.

CriteriaConformance LevelRemarks and Explanations
1.2.4 Captions (Live) (Level AA)Web: Not ApplicableComponents: No component plays media. bestax.io: The site has no live media.
1.2.5 Audio Description (Prerecorded) (Level AA)Web: Partially SupportsComponents: No component plays media. bestax.io: The film embedded in the Image page's example has no audio description (#2224).
1.3.4 Orientation (Level AA, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: SupportsComponents: Nothing locks the display to one orientation. bestax.io: No known gaps.
1.3.5 Identify Input Purpose (Level AA, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: SupportsComponents: Input and Select pass autoComplete through, so an app can name the purpose of a field that collects personal information. Combobox, Autocomplete and DateRangeInput turn the browser's autofill off, so it doesn't cover their own lists, and so aren't the controls for such a field. bestax.io: The site collects no personal information.
1.4.3 Contrast (Minimum) (Level AA)Web: Partially SupportsComponents: Bulma's stock info, success, warning and danger colors fall short of 4.5:1 as text on white and on Bulma's light greys, and so does its grey text in places, on both schemes (#2188, next major, which also lists bestax's own shades that fall short). Slider's value bubble text (#2192) and bold text and links inside a Tooltip (#2191) fall short on some colors, and so does a color's text on a colored surface (#1694, #1695, next major). bestax.io: The footer's links, the code highlighting, and the homepage's hero and banner fall short (#2215, #2207, #2208).
1.4.4 Resize Text (Level AA)Web: SupportsComponents: Bulma sizes text in rem and em, so it follows the browser's text size and zoom. bestax.io: No known gaps.
1.4.5 Images of Text (Level AA)Web: SupportsComponents: No component draws text as an image. bestax.io: The only images of text are logos.
1.4.10 Reflow (Level AA, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: Partially SupportsComponents: Layouts wrap at narrow widths. Without isResponsive a DataTable or Table has no scroll box of its own, so with Bulma's default overflow-x: hidden on the page, one wider than a narrow screen has its last columns cut off (#2256, next major). With it, a wide table scrolls inside itself, which WCAG allows for content that needs two dimensions. bestax.io: No known gaps.
1.4.11 Non-text Contrast (Level AA, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: Partially SupportsComponents: AppFrame's resize line is low contrast on Bulma's own primary (#1761), and some controls drawn in Bulma's stock colors fall short of 3:1 (#2188, next major). bestax.io: Covered by the site's contrast issue (#2215).
1.4.12 Text Spacing (Level AA, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: SupportsComponents: No known gaps, judged from the CSS rather than tested on every component. bestax.io: No known gaps.
1.4.13 Content on Hover or Focus (Level AA, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: SupportsComponents: A shown Tooltip lets the pointer move onto it, stays while the pointer or focus is on its trigger or on it, and closes on Escape wherever focus is. bestax.io: No known gaps.
2.4.5 Multiple Ways (Level AA)Web: SupportsComponents: A site's criterion, the app's. bestax.io: Pages can be reached through the navbar, the sidebars and the search.
2.4.6 Headings and Labels (Level AA)Web: SupportsComponents: Headings and labels carry the app's words. bestax.io: No known gaps.
2.4.7 Focus Visible (Level AA)Web: Partially SupportsComponents: Components draw Bulma's focus ring, and in forced colors a ring in the system's colors. Known gaps: a focused read-only field draws no ring (#2128), and in forced colors shows only a thin border change (#2087); in forced colors, a read-only DateRangeInput, or a Taginput at its limit, shows focus only by its box's border color (#2161); a selected toggle tab's link has no ring in the focus color (#1945). bestax.io: The live code examples' editor shows no focus ring (#2180).
2.4.11 Focus Not Obscured (Minimum) (Level AA, WCAG 2.2 only; Revised Section 508 and EN 301 549 do not apply)Web: Partially SupportsComponents: With a fixed-top Navbar, Shift+Tab can scroll the focused control under the bar (#2193). bestax.io: No known gaps.
2.5.7 Dragging Movements (Level AA, WCAG 2.2 only; Revised Section 508 and EN 301 549 do not apply)Web: Partially SupportsComponents: Slider takes a click on its track and its keys as well as a drag, and Carousel has buttons beside its swipe. Splitter and AppFrame's resizable column need a drag to set a size with a pointer (#2197), and a zoomed Lightbox image pans only by dragging (#2231). bestax.io: No known gaps.
2.5.8 Target Size (Minimum) (Level AA, WCAG 2.2 only; Revised Section 508 and EN 301 549 do not apply)Web: Partially SupportsComponents: Below the 24px minimum without the spacing that would excuse it: Carousel's indicators (#1926), a small Switch (#1972), a small Rate's stars (#1973), Numberinput's stepper buttons (#1974), a range Slider's thumbs (#2195), and the clear buttons on Cascader and TreeSelect and Delete itself (#2198). bestax.io: The blog's author social links (#2218).
3.1.2 Language of Parts (Level AA)Web: SupportsComponents: LocaleProvider sets lang on the part of the page it wraps. The language of an app's text is the app's to mark. bestax.io: No known gaps.
3.2.3 Consistent Navigation (Level AA)Web: SupportsComponents: A site's criterion, the app's. bestax.io: The navbar, sidebars and footer are the same on every page.
3.2.4 Consistent Identification (Level AA)Web: Partially SupportsComponents: Components name the same function the same way, with one known exception: Message's close button is named "delete" where every other close button is "Close" (#1912, next major). bestax.io: No known gaps.
3.3.3 Error Suggestion (Level AA)Web: SupportsComponents: A form control's message shows the suggestion the app writes, tied to the control through aria-describedby. bestax.io: The site has no forms beyond its search.
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA)Web: Not ApplicableComponents: A process's criterion, the app's. bestax.io: The site takes no legal, financial or personal data.
3.3.8 Accessible Authentication (Minimum) (Level AA, WCAG 2.2 only; Revised Section 508 and EN 301 549 do not apply)Web: SupportsComponents: PasswordInput allows pasting and password managers, and no component asks for a cognitive test. bestax.io: The site has no sign-in.
4.1.3 Status Messages (Level AA, WCAG 2.1 and 2.2; Revised Section 508 does not apply)Web: Partially SupportsComponents: Toast, CopyButton, Command, TreeView and the range pickers announce their messages through live regions without moving focus. A loading form field says nothing to a screen reader unless the app describes it (#2135). bestax.io: No known gaps.

Table 3: Success Criteria, Level AAA​

Notes: Level AAA isn't included in this report.

Revised Section 508 Report​

Notes: The WCAG tables above also cover Chapter 5's 501.1 and Chapter 6's 602.3.

Chapter 3: Functional Performance Criteria (FPC)​

Notes: Each answer weighs the known gaps in the WCAG tables against the functional need. None has been tested with real assistive technology (see Evaluation Methods Used).

CriteriaConformance LevelRemarks and Explanations
302.1 Without VisionPartially SupportsComponents expose names, roles and states, which unit tests and axe check. Some names and roles are wrong until the next major (WCAG 4.1.2), and nothing has been tested with a real screen reader.
302.2 With Limited VisionPartially SupportsText follows the browser's zoom and text size (WCAG 1.4.4), but some colors fall short of contrast (WCAG 1.4.3 and 1.4.11, #2188, #2215), some targets are small (WCAG 2.5.8), some focused controls show no ring or a faint one (WCAG 2.4.7), and a wide DataTable or Table without isResponsive is cut off at the edge of a narrow screen (WCAG 1.4.10, #2256, next major).
302.3 Without Perception of ColorPartially SupportsLinks in running text and Timeline's markers rely on color alone (WCAG 1.4.1, #1858, #1991, #2203).
302.4 Without HearingPartially SupportsNo component needs hearing. The site's one embedded film has no captions (WCAG 1.2.2, #2224).
302.5 With Limited HearingPartially SupportsAs 302.4.
302.6 Without SpeechSupportsNothing needs speech.
302.7 With Limited ManipulationPartially SupportsThe components work from the keyboard, with the gaps in WCAG 2.1.1. Some targets are under 24px (WCAG 2.5.8), and Splitter, AppFrame's resizable column and a zoomed Lightbox need a drag with a pointer (WCAG 2.5.7, #2197, #2231).
302.8 With Limited Reach and StrengthSupportsBestax is used through the device's own input and needs no reach or strength of its own.
302.9 With Limited Language, Cognitive, and Learning AbilitiesPartially SupportsA plain Toast closes after two seconds by default, and a programmatic notification after three (WCAG 2.2.1, #2196, #2233), an autoplaying Carousel can't be stopped (WCAG 2.2.2, #1925), and on the homepage a demo moves focus and a carousel plays on its own (#2204, #2206).

Chapter 4: Hardware​

Notes: Bestax is not hardware, so the requirements of this chapter do not apply.

Chapter 5: Software​

Notes: Bestax is web content: a library that renders HTML in a browser, and a website. It reaches assistive technology through the browser, not through platform accessibility services of its own, so the software rows in 502 and 503 don't apply to it, and its conformance is in the WCAG tables. It isn't an authoring tool.

CriteriaConformance LevelRemarks and Explanations
501.1 Scope – Incorporation of WCAG 2.0 AASee WCAG 2.x sectionSee the WCAG tables.
502 Interoperability with Assistive Technology (502.2.1 to 502.4)Not ApplicableWeb content, which reaches assistive technology through the browser; see the WCAG tables.
503 Applications (503.2 to 503.4.2)Not ApplicableWeb content, which reaches assistive technology through the browser; see the WCAG tables.
504.2 Content Creation or EditingNot ApplicableBestax isn't an authoring tool. It has no editor, and the content an app builds with it is the app's.
504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot ApplicableNot an authoring tool.
504.2.2 PDF ExportNot ApplicableNot an authoring tool.
504.3 PromptsNot ApplicableNot an authoring tool.
504.4 TemplatesNot ApplicableNot an authoring tool.

Chapter 6: Support Documentation and Services​

CriteriaConformance LevelRemarks and Explanations
602.2 Accessibility and Compatibility FeaturesSupportsThe API pages on bestax.io have an Accessibility section on each component's keyboard support, names, roles and states, and forced colors, except the layout-only Columns and Grid parts, and the accessibility statement describes the rest.
602.3 Electronic Support DocumentationSee WCAG 2.x sectionbestax.io is the documentation, and the WCAG tables cover it.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot ApplicableThere is no non-electronic documentation.
603.2 Information on Accessibility and Compatibility FeaturesSupportsSupport happens in GitHub issues and on Discord, where answers can point to each component's Accessibility section and the accessibility statement.
603.3 Accommodation of Communication NeedsPartially SupportsSupport is in writing, through GitHub issues and Discord. There's no phone, email or relay channel, so someone who can't use either has no way in.

EN 301 549 Report​

Notes: The WCAG tables above also cover Clause 9, and Clauses 12.1.2 and 12.2.4.

Chapter 4: Functional Performance Statements (FPS)​

Notes: Each answer weighs the known gaps in the WCAG tables against the functional need, as in the Revised Section 508 Report's Chapter 3.

CriteriaConformance LevelRemarks and Explanations
4.2.1 Usage without visionPartially SupportsAs 302.1.
4.2.2 Usage with limited visionPartially SupportsAs 302.2.
4.2.3 Usage without perception of colourPartially SupportsAs 302.3.
4.2.4 Usage without hearingPartially SupportsAs 302.4.
4.2.5 Usage with limited hearingPartially SupportsAs 302.4.
4.2.6 Usage with no or limited vocal capabilitySupportsNothing needs speech.
4.2.7 Usage with limited manipulation or strengthPartially SupportsAs 302.7.
4.2.8 Usage with limited reachSupportsBestax is used through the device's own input and needs no reach of its own.
4.2.9 Minimize photosensitive seizure triggersSupportsNothing flashes (WCAG 2.3.1).
4.2.10 Usage with limited cognition, language or learningPartially SupportsAs 302.9.
4.2.11 PrivacySupportsNo accessibility feature exposes private information.

Chapter 5: Generic Requirements​

CriteriaConformance LevelRemarks and Explanations
5.1 Closed functionality (5.1.2 to 5.1.6)Not ApplicableBestax works with the browser and assistive technology the user brings, so it has no closed functionality.
5.2 Activation of accessibility featuresSupportsBestax has no accessibility features of its own to turn on. It follows the browser's and the system's settings, such as forced colors and reduced motion.
5.3 BiometricsNot ApplicableNothing uses biological characteristics.
5.4 Preservation of accessibility information during conversionNot ApplicableBestax converts nothing from one format to another.
5.5 Operable parts (5.5.1 and 5.5.2)Not ApplicableBestax has no physical parts.
5.6 Locking or toggle controls (5.6.1 and 5.6.2)Not ApplicableBestax has no physical locking or toggle controls.
5.7 Key repeatNot ApplicableBestax has no physical keyboard; key repeat is the system's.
5.8 Double-strike key acceptanceNot ApplicableBestax has no physical keyboard.
5.9 Simultaneous user actionsSupportsNothing needs two actions at once.

Chapter 6: ICT with Two-Way Voice Communication​

Notes: Bestax has no two-way voice communication, so the requirements of this chapter do not apply.

Chapter 7: ICT with Video Capabilities​

Notes: No component plays video. The site's one embedded film plays in YouTube's player, which is YouTube's, and its missing captions and description are under WCAG 1.2.2, 1.2.3 and 1.2.5. The requirements of this chapter do not apply to Bestax.

Chapter 8: Hardware​

Notes: Bestax is not hardware, so the requirements of this chapter do not apply.

Chapter 9: Web​

See the WCAG 2.x section.

Chapter 10: Non-Web Documents​

Notes: Bestax ships no non-web documents, so the requirements of this chapter do not apply.

Chapter 11: Software​

Notes: Bestax is web content, so its requirements are covered in Clause 9 and, through it, the WCAG tables (clause 11.0, note 2). It isn't an authoring tool. The requirements of this chapter do not apply.

Chapter 12: Documentation and Support Services​

CriteriaConformance LevelRemarks and Explanations
12.1.1 Accessibility and compatibility featuresSupportsAs 602.2.
12.1.2 Accessible documentationSee WCAG 2.x sectionbestax.io is the documentation, and the WCAG tables cover it.
12.2.2 Information on accessibility and compatibility featuresSupportsAs 603.2.
12.2.3 Effective communicationPartially SupportsAs 603.3.
12.2.4 Accessible documentationSee WCAG 2.x sectionAs 12.1.2.

Chapter 13: ICT Providing Relay or Emergency Service Access​

Notes: Bestax provides no relay or emergency service access, so the requirements of this chapter do not apply.


“Voluntary Product Accessibility Template” and “VPAT” are registered service marks of the Information Technology Industry Council (ITI).