Our target
We aim for renderloria.online to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. In Ontario, the Accessibility for Ontarians with Disabilities Act requires designated public sector bodies, and private or non-profit organizations employing at least 50 people, to make their public websites conform to WCAG 2.0 at level AA (source 1); we hold ourselves to the newer version even though that requirement may not apply to us.
What we have done
- Built pages with semantic HTML: one main heading per page, ordered headings, landmarks for header, navigation, main content and footer, and a skip link.
- Checked colour contrast for text against its background with a script, targeting at least 4.5 to 1 for normal text, and checked that focus outlines contrast at least 3 to 1 with the backgrounds around them.
- Made every control usable with a keyboard and kept a visible focus outline on links, buttons and form fields.
- Sized buttons and form controls to at least 24 by 24 CSS pixels, with main buttons at least 44 pixels high.
- Given every form field a visible label. Errors are announced in a summary that receives focus, link to the fields, and are described on each field.
- Made the free tools give their results as text and tables, not only as charts, and move focus to the result when you submit.
- Made the site usable without JavaScript, apart from the free tools, which explain their models in text.
- Respected the reduced motion setting in your operating system; the site uses no autoplaying animation.
- Tested layouts at widths from 320 pixels upwards and with text zoom.
What we have not done yet
We have not yet tested the site with screen reader users or other disabled people, and we have not run a full manual audit with assistive technologies. Both are planned: we intend to complete them by March 31, 2027 and will update this statement with what we find.
Known limits
- The illustrative dashboards and before-and-after panels are decorative pictures of a report. Their text is summarized in captions and nearby paragraphs, and the parts that carry no meaning are hidden from assistive technologies.
- Code samples in guides are wide and scroll sideways on small screens. Each code block can receive keyboard focus so it can be scrolled with arrow keys.
- Some linked sources, such as framework documentation, are outside our control and may not meet the same standard.
Report a barrier
If something on this site is hard or impossible for you to use, please tell us at hello@renderloria.online. Describe the page and the problem, and the browser or assistive technology you use if you are comfortable sharing it. We read every report and reply by email, and we fix barriers as quickly as we can. We can also send content in another format on request.
Sources
- How to make websites accessible, Government of Ontario Primary source (government)