Nexus Standards · Accessibility
WCAG 2.2 AA
Accessibility statement
This site is designed to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA: a single heading structure per page, keyboard operation of every instrument, visible focus, touch targets of at least 36 px at phone width, text contrast of 4.5:1 and non-text contrast of 3:1 in both light and dark themes, respect for reduced-motion preferences, and every figure readable without script. This statement is a self-assessment.
Summary
- LevelWCAG 2.2 AA
- Keyboardevery instrument: arrow keys, plus and minus, Enter, Escape, and the letters named in each instrument's label
- Motionno idle animation when reduced motion is requested
- Themeslight and dark, from the same design tokens
- Scriptevery figure and table renders without it
Nexus Standards · proposed
Known limitations
- The globe and the crosswalk graph are drawn on canvas. Their content is also provided as a still figure, a table and a detail panel that screen readers can read, but the canvas itself carries no per-feature text.
- Colour on the coverage matrix is accompanied by a legend and cell labels; the cross-highlighting on hover has no screen-reader equivalent beyond the cell label.
- The WordPress theme that hosts these pages is outside the scope of this statement.
Reporting an accessibility barrier
Barriers may be reported to contact@therisk.global, stating the page address and the difficulty encountered. The horizontal review group for accessibility reads each report. The response time is fourteen days.
Questions and answers.
Is this statement an accessibility certification?
Contribute to Nexus Reports from this page.
Nexus Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
- GatewayGW-STDSend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Nexus Reports community. Curators review it there; the DOI stays yours.
- Nexus ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Around the Nexus Standards.
Take part in the standards.
Governments, regulators, standards bodies, industry, academia and communities are invited to shape the catalogue ahead of its first official release, targeted for 2030: comment on a draft, propose a change, join a working group or host a field exercise.
Status and use. The Nexus Standards are proposed standards developed through an open process under NS-13 and published for voluntary use; they do not constitute certification, accreditation or regulatory approval, and adoption remains a decision of the Global Standards Council and, in each country, of its National Standards Council. A UNI (Unique Nexus Identifier) identifies an artifact; it does not certify it. Names of standards bodies and their standards belong to their stewards and are used only to identify the documents; no text of an external standard is reproduced here. Nexus Standards is not affiliated with, endorsed by or certified by any standards body named here.
Licences: CC BY 4.0 for standards text, registries, schemas and data; Apache-2.0 for reference code. External standards are cited by name, number and link under their own licences. Third-party data, libraries and fonts keep their own licences: see Third-party notices.