Statement
Braillito accessibility statement
What we have done so that Braillito can be used with a screen reader and with low vision, what we have not verified yet, and how to tell us if you run into a barrier.
Our commitment
Braillito teaches braille. It would make no sense if the tool you learn with could not be used by the people who need it most, so the goal is concrete and testable: a blind person and a sighted person must be able to learn in the same app, doing the same exercises and moving along the same path.
There is no separate “accessible version”. In the web version, setup asks whether you use a screen reader; on iPhone and Android, the app detects VoiceOver and TalkBack by itself. Either way it adapts the interface and the exercises, and it is still the same app with the same content. When something only works by looking at the screen, we treat it as a bug, not as an acceptable limitation.
Measures we have put in place
These are the accessibility decisions already in the product, and you can check them by using it.
- Atkinson Hyperlegible typeface Designed by the Braille Institute of America for low-vision readers: its letters are drawn to be told apart rather than to look alike, which is where ordinary typefaces fail.
- High-contrast mode A visible control in the header of every page switches the whole palette to maximum contrast. The preference is remembered between visits.
- Skip links The first keyboard stop on every page is a link that jumps straight to the main content, without going through the whole navigation.
-
Semantic markup and named regions
Each section is tied to its heading with
aria-labelledby, so a screen reader’s region and heading navigation returns a useful list instead of a pile of unnamed blocks. - Works with VoiceOver and TalkBack The app is used with VoiceOver on iOS and TalkBack on Android, and with desktop screen readers in the web version.
-
Accessibility declared in structured data
The site publishes
accessibilityFeature,accessModeandaccessModeSufficientin its structured data, so search engines and educational catalogues know the content can be used with text alone or audio alone. - Shape does not depend on colour alone In the braille cell, raised dots are told apart from flat ones by their fill, not only by their colour, so they read the same in light mode, dark mode and high contrast.
-
prefers-reduced-motionis respected If your system asks for reduced motion, this website’s animations are turned off; none of them carries information that is not also in the text.
Conformance level
We aim for the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA, and we cannot yet claim to meet them. We have not completed an external audit or a formal conformance evaluation, so declaring a specific level would be claiming something nobody has checked.
What we can say is what the previous section lists: concrete measures, already in place, that you can verify by using the product. We keep working towards level AA, and this statement will be updated when there is an evaluation that supports something stronger.
Why we put it this way. An accessibility statement that promises conformance without an audit harms exactly the people who read it to decide whether they can use the tool. We would rather fall short and have everything we claim be true.
This statement is voluntary. Braillito is a product of a private Peruvian company, so the European directive 2016/2102, which requires public-sector bodies to publish an accessibility statement, does not apply to it. We publish one anyway: a product that exists to make reading accessible and does not declare its own accessibility contradicts itself. The evaluation has been an internal self-assessment, not a third-party audit.
Known limitations
No app is ever finished in accessibility. These are the areas where we know we are not there yet:
- There is no external audit. Nobody outside the team has formally evaluated the product against WCAG.
- We have not tested every combination. There is no systematic test run with every screen reader, browser and operating system; our checks focus on VoiceOver and TalkBack.
- Refreshable braille displays. The text in the app is real text, so a braille display shows it automatically, but we have not run specific tests with each model.
- The mini-games are not all alike. There are sixteen different mechanics, and not all of them have been reviewed in the same detail. If one does not work for you with your screen reader, we want to know which.
- Content we do not control. The App Store, Google Play and third-party pages we link to are outside our reach.
The detailed version, screen by screen and with what is in our code, is in Using Braillito with VoiceOver and TalkBack.
Tell us if something does not work for you
This is the useful part of the statement. If a screen cannot be read with your screen reader, an exercise cannot be finished without sight, the contrast is not enough for you or something is lost when you enlarge the text, write to us and tell us which page or lesson it was, on which device and with which screen reader.
Reports of specific barriers are what actually moves this list. We treat them as bugs, not as suggestions.
We reply within 5 business days at most. If you would rather not use the website, or if the website is precisely what is not working for you, you can write to us or call us on +1 305 462 4160.
Scope of this statement
This statement covers the website braillito.com and the Braillito web app opened from it. It does not cover the native iOS and Android apps, which have not been evaluated yet. We would rather limit the scope to what has been reviewed than sign something we have not checked.
This is an English translation of the Spanish statement, which prevails if the two ever differ.
Try it with your screen reader
The same app for blind and sighted learners
Braillito teaches braille from scratch, with 63 lessons and 16 mini-games in 38 languages, English included.
Works with VoiceOver and TalkBack