Accessibility statement
We want anyone to be able to use Chord and Fret on the web: people who listen to pages with a screen reader, use only the keyboard, zoom in or switch on high contrast. We follow the international web accessibility guidelines, check the site before every release and want to hear when something gets in your way.
The standard we follow
Our target is level AA of WCAG 2.2, the Web Content Accessibility Guidelines published by the W3C, the international consortium that sets the standards of the web. In practice, it is a list of requirements that make a site usable by people with visual, hearing, motor or cognitive disabilities, and by anyone who needs to read and navigate in a different way. WCAG has three levels, A, AA and AAA; AA is the one laws and standards usually ask for.
Chord and Fret is run by a Brazilian company, so the site also answers to the Brazilian Inclusion Law (Law 13.146/2015), which requires company websites to be accessible according to the international guidelines.
Current status: partially conformant
This site is partially conformant with WCAG 2.2 level AA. That means we have not yet verified every requirement with people and with assistive technologies; it does not mean we know of a barrier and left it in place.
We use the W3C term “partially conformant” because we cannot yet guarantee that every part of the site meets every requirement: the evaluation by people, described below, is still missing.
Before any release goes live, the site runs through automated checks, and the release stops if any of them finds a problem.
What has not been done yet is a manual evaluation with assistive technologies, that is, the software and settings people with disabilities use to get around, such as screen readers, which read out loud what is on the screen: NVDA (on Windows), VoiceOver (on iPhone and Mac) and TalkBack (on Android). Testing the site with people who use these technologies every day is still to come as well. No automated check replaces that.
What we check on every release
Some of the checks read every page of the site. The others open the pages in a browser, the way a person would, and test examples of each kind of page (chords, scales, strumming, tools and the rest) in all three languages.
- Every page declares its language, so the screen reader pronounces the words correctly.
- Every page has a title, one main heading and subheadings in order, without skipping a level.
- Images and drawings, such as the chord diagrams, have a text description.
- Every link, button and form field has a name the screen reader announces, and that name contains the text shown on screen, for people who control the computer by voice.
- There is a link to skip straight to the content, and the menus at the top and bottom keep the same order on every page. Support and this statement always sit in the same place in the footer.
- The automated tool axe-core, which flags accessibility problems, checks every tested page in the light theme, in the dark theme and at phone size, including the contrast between text and background.
- Keyboard navigation: as you move through the page with the Tab key, the focus (the marker that shows where you are) is always visible, is never hidden behind the cookie notice or fixed bars and never gets stuck in one place; and Shift+Tab goes back the same way.
- On phones, buttons and standalone links (not the ones inside a sentence) are at least 24 by 24 pixels, or have free space around them, so a tap does not hit the one next to it.
- The page fits a screen 320 pixels wide, the same as 400% zoom on a computer, and one 640 wide, the same as 200% zoom, without sideways scrolling and without cutting text off.
- With extra space between lines, letters and words, no text gets cut off.
- In Windows forced colors, the high contrast mode that swaps the site’s colors for the system’s, the focus stays visible, icons do not disappear and a button that is switched on still looks different from the others.
- For anyone who asks the system for less motion on screen, no animation keeps running.
Known limitations
The text descriptions of the drawings have not yet been reviewed by people who use screen readers, and some say little. For a chord diagram, the description gives the fret of each string as numbers, such as “x 3 2 0 1 0” (the x marks a string you do not play); for a strumming grid, it repeats the letters and arrows of the pattern; for a scale diagram, it only says how many strings and frets are shown, not where the notes are.
The automated checks find no other barrier. If you find one, please tell us.
How to report a barrier
If something on the site gets in your way (a button the screen reader does not announce, text that disappears when you zoom, a color that is hard to read), write to suporte@cifraebraco.app. Tell us which page it was, what happened and, if you can, the browser and the assistive technology you use.
We answer within 5 days, the same deadline as Support. Support →
What about the app?
The Chord and Fret app has an accessibility review of its own. Reports about the app are welcome at the same address too.
About this statement
- Written on October 21, 2026, based on a self-assessment, that is, a review done by our own team, with no external audit.
- The site’s last accessibility review was on October 20, 2026.
- It covers chordandfret.app and the Portuguese (cifraebraco.app) and Spanish (acordeytraste.app) versions, which go through the same checks. Pages of other companies the site links to, such as the app stores, are not covered.