Papaye Links
Check Papaye Links buttons on a mobile screen
Review your public page on a small screen and with a keyboard to find links that are difficult to read, reach or understand.
Read button labels on their own
Try reading the labels without the rest of the page. “See Saturday’s schedule” describes the destination more clearly than “More information.” WCAG explains how the purpose of a link can be conveyed through its text or context. On a links page, standalone labels often provide the clearest choice.
Test the page on a phone
Check that important text stays readable when you enlarge the font and that adjacent buttons can be activated independently. WCAG criterion 2.5.8 specifies a minimum target size of 24 × 24 CSS pixels or sufficient spacing, subject to its conditions and exceptions. A phone check can help reveal accidental taps.
Navigate with a keyboard
Open the public page on a computer and move through it with Tab. Check that you can see the focused button, that the sequence makes sense and that Enter opens the expected destination. Review any controls on the destination page as well, such as a booking form.
Follow the full path to an action
Try a complete task, such as reading the schedule after opening the corresponding link. Check the content, forms and sign-in requests on the linked service. Visitors should be able to tell where they landed, including when a link opens a different domain.
Checklist
- Read every label on its own.
- Try the page with larger text on a phone.
- Navigate by keyboard and check that focus is visible.
- Complete one action from the public page.