Accessibility statement
Accessibility features and how to report a barrier.
Report an accessibility barrier through the contact form. Include the page address, the task you could not complete and the browser or assistive technology involved. For a calculator, identify the input or result that caused the problem; omit personal information.
Reading and using the controls
The page shell includes a skip link to the main content. Tables use captions and header cells. Calculator fields have labels, and contact-form errors use an alert region.
- These features describe the markup
- They do not establish compatibility with every browser or assistive tool.
Browser zoom enlarges text. Wide tables can require horizontal scrolling. Specification references can lead to external PDF documents whose accessibility depends on their publisher.
When reporting a PDF barrier, include its address as well as the page that links to it.
Reporting a blocked task
Describe what you expected and what happened, including any text announced by a screen reader or displayed in an error. A keyboard issue is easier to locate with the control name and the sequence of keys involved.
- Legal
- Accessibility statement; Accessibility here means the pages and calculators work by keyboard and screen reader, and reports of barriers are fixed.
Accessibility
Motorcycle ATV UTV Specs aims for WCAG 2.2 level AA, with keyboard operation, screen-reader structure and readable tables as design goals; an individual browser or assistive-technology combination can still expose a barrier that needs to be reported and corrected. Pages are plain HTML. Headings run in order and text reflows on a phone. A blocked control or unreadable passage can be reported through the contact form. Name the page and the device or assistive tool you used.
A useful report names three things:
The page address
What you were trying to do and what stopped you
The device, browser or assistive tool you used
Accessibility of the pages
Each page has one main heading, and the section headings follow it in order. A screen reader can list them and jump between sections. Spec tables carry a caption and header cells, so a reader hears the row label before the value. Images that carry meaning have text alternatives. Decorative ones are marked so a screen reader skips them.
Color is never the only signal. Links are underlined in body text. Nothing on a page moves by itself. Focus outlines stay visible as you tab. Text enlarges in the browser without losing content.
Accessibility of calculators and forms
Every calculator field has a visible label tied to its input, and a unit. An out-of-range value gets an error message that names the field. A rejected value is explained and never changed for you. The result appears as text that a screen reader can read out in full, not only as a color or a chart. The contact form works the same way.
Its hidden anti-spam field is skipped by screen readers and by keyboard users.
How accessibility is checked
Automated accessibility checks can identify missing labels, heading problems and missing image alternatives; they cannot establish whether a particular table, error message or keyboard sequence makes sense to the person using it. The calculators are also tested on ordinary, edge and invalid values. Automated checks find some problems and miss others, such as an awkward reading order. So we fix what readers report. The form accepts the page address, task and barrier description for investigation; it does not promise a response within a fixed period.
Accessibility questions
Does this site work with a screen reader?
Yes, that is what the page structure is built for. Each page has one main heading with section headings in order, spec tables carry captions and header cells, and controls have labels tied to them.
Can I use the calculators with only a keyboard?
Yes. Every field, button and result can be reached and operated with the Tab and Enter keys, and the focus outline stays visible so you can see where you are on the page.
Which accessibility standard does the site aim for?
We aim for the Web Content Accessibility Guidelines 2.2 at level AA. That is a target we work toward and check, and a report of a barrier tells us where we have not reached it.
How do I report an accessibility problem on a page?
Use the contact form and name the page, describe what blocked you, and say which device, browser or assistive tool you were using. A person reads each report and answers through the form.
Are the spec tables readable by a screen reader?
They are built as real tables with a caption and header cells. A screen reader announces the row label before each value, so a figure is never read out without the name of the thing it measures.
Can I enlarge the text on these pages?
Yes. Text can be enlarged in the browser without losing content, and the layout reflows to a single column on a narrow screen such as a phone.
Do the pages rely on color alone to show meaning?
No. Links in body text are underlined and calculator errors are written out in words that name the field, so nothing depends on telling one color from another.
How are calculator results shown to a screen reader?
The result appears as text on the page, with the formula and a worked example beside it, so a screen reader can read the answer and the working in full instead of relying on a chart or a color.
What happens after I report an accessibility barrier?
The report is read by a person, the problem is reproduced where it can be, and the page is fixed. If the cause is a document on another site, we state the figure in our own page text instead.
Are the manufacturer documents you link to accessible?
Not always. Specification sheets and standards are often PDF files published by other organizations, so where a fact is needed from one we give the figure in the page text and you do not have to open the file.
Is there a way to contact you without a phone call?
Yes. The contact form is the only route and needs no phone call. It has labelled fields, and a hidden anti-spam field that screen readers and keyboard users skip.
Do the pages work on a phone?
Yes. The layout reflows to one column on a narrow screen, and you can enlarge the text in your browser without losing any content.