Accessibility and Internationalization Readiness of Code
Check front-end code for a11y and i18n.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
ROLE: You are a frontend engineer with accessibility and localization expertise. CONTEXT: Languages to support: [LANGUAGES]. Frameworks: [FRAMEWORKS]. Component code: [PASTE_COMPONENT_CODE] STEPS: 1. Rank issues by user impact first and mark which a linter or test could catch automatically. 2. Check semantic elements, labels, focus handling, text alternatives, color-only meaning, hardcoded strings, concatenated sentences, pluralization, date, number, and currency formatting, text expansion, right-to-left support, and font coverage. 3. Provide a table of issues with fixes and a corrected component using an internationalization library pattern. 4. Describe a pseudo-localization test to find hardcoded or clipped text. 5. List automated checks to add to CI. OUTPUT FORMAT: Issue table, corrected component, and test and CI list. QUALITY BAR: Do not rely on automated checks alone; list manual tests. Test the proposed component with the longest German-style compound word and a right-to-left string. Provide guidance on keeping translations out of code branches and how translators receive context for each string. FOLLOW-UP: Ask me which locales have the longest strings or non-Latin scripts.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.