Accessibility: what we checked and what is still not good enough

Checked: November 5, 2026

We want everyone to be able to use URIDA, including people who use a keyboard, a screen reader, large text, or their voice. This page says what we checked ourselves, what we found, and what is still not good enough. We do not claim that the site meets WCAG or any other accessibility standard, and no outside expert has audited it.

URIDA is not a government agency.

What we checked, and how

On November 5, 2026 we checked: the home page (Korean and English), the guide's consent screen and first speaking step, the programs list, a program page, a state page, and the privacy and trust pages.

We ran the free axe-core 4.10.2 scanner in a browser on local copies of those pages, which do not load ad code, so ads and what is inside ad frames were not checked. We walked through the home page at desktop width with the keyboard only (all 29 stops), tried the three text sizes and a narrow phone-width screen, and read the code for button and link names. After the last fixes listed below we measured text size and page width again in a browser, but we did not run the scanner again.

We did not use a screen reader such as NVDA, JAWS, or VoiceOver, and we did not test with people who have disabilities.

What we found

• Keyboard: on the home page at desktop width the Tab key moves through the page in a sensible order, all 29 stops show a visible outline, and we found no place where the keyboard gets stuck. The accessibility settings window closes with the Esc key.
• Contrast: the scanner found one text-contrast problem on the first screen (the card number was 4.25 to 1; the minimum is 4.5 to 1) and we fixed it. For 33 pieces of text the scanner could not decide because they sit over gradients (29), use special characters (3), or come from a decorative style (1); our own calculation, which treats those backgrounds as flat, found none below the minimum. Treat that as an estimate.
• Text size: Accessibility settings offer three sizes (16, 19, and 22 pixel base text, up to about 137 percent), remembered on your device. Our first check found that part of the text on the home page and the guide did not change size; we fixed that. Body text on the home page, the consent screen, and the first speaking step now follows the setting. Large headings, the top bar, and the label on the accessibility button do not. At 375 and 640 pixels wide (640 is what a 200 percent browser zoom on a 1280-pixel screen gives), those three screens did not scroll sideways at any of the three sizes. The privacy page scrolled sideways on a phone because of long links; we fixed that too.
• Names for screen readers: the scanner found no buttons, links, or form fields without a name on the pages we scanned. It found two nested page-region labels (the accessibility tool group and the donation card), and we fixed them. On the first speaking step it flagged a label on text that had no role allowed to carry one; we fixed the code and confirmed the change in the browser, but did not run the scanner again. On the home page and in the guide the page language is set for each of the 13 languages, and Arabic switches to right-to-left.
• Voice: everything that can be done by voice can also be done by tapping or typing. The Speak button works only when your browser can recognize speech on your own device; otherwise it is not used and the guide points you to tapping. Reading aloud picks a voice for each language from your browser, so how good it sounds depends on the voices on your device.

What is still not good enough

• No screen reader testing yet, and no testing with disabled users. The scanner finds only part of the problems.
• We have not yet scanned the later steps of the guide (documents and results), application preparation, document scan, or the form filling screens. Problems there are possible.
• Translations into languages other than English and Korean are made with AI and have not been reviewed by native speakers. We checked Arabic right-to-left layout only for the new text on the first screen.
• Text size goes up to about 137 percent in our settings. For larger text, use your browser's zoom. The text size setting is only on the home page and in the guide, not on program, state, trust, privacy, or this page.
• There is no skip link. A keyboard user passes 8 stops before reaching the main content of the home page.
• At phone width the Tab order does not always follow the order on screen.
• The short how-to video on the consultation preparation page (/prepare) has Korean captions only and no sound. That page is in Korean only, and its language setting wrongly says English, so a screen reader may read it badly.
• The 33 contrast items above need a check by a person or a better tool.
• The accessibility link on the home page opens the English page in the 11 languages other than English and Korean.
• On the state page, which is very long, the scanner's contrast check covered only the top of the page; its other checks covered the whole page.
• When we switched the home page to Arabic, the scanner flagged the contrast of one language button once; a repeat scan found nothing. We do not know whether it is a real problem.
• irovena.com may show Google automatic ads, and we cannot change what is inside an ad. The bar at the top of the screen is our own. For now it shows only our own notice. It stays in place and has no close button. The official pages and forms we link to belong to the agencies, and we cannot fix their accessibility. Some official forms are PDF files that may not work well with a screen reader.

Tell us about a barrier

If something is hard to use, write to support@irovena.com with the page address, what you were trying to do, and the device, browser, or assistive technology you use. A person reads it. We will tell you what we can change; we cannot promise a date. Do not send Social Security, bank, or card numbers.

Back to how this site is made.