AucertAucertWikipedia (Android App) app review Download PDF
Sample report

Wikipedia Android app

An expert review of Wikipedia (Android App) for Android: what Aucert’s agents found on 37 screens, why it happens, and what to fix first.

37screens checked
36confirmed issues
21 minautomated scan
Illustrative preview · October 2026
Executive summary

36 confirmed issues.
Three patterns cause 58%.

Iris, Genie and Pax checked the 37 screens the scan reached in Wikipedia’s Android app. Most of what they found is a short search bar, tabs that don’t say they’re selected and small icons.

37
screens checked in 21 minutes
28
screens with at least one confirmed issue
36 dp
height of the article search bar; Android asks for 48 dp
6
selected feed tabs that don’t tell a screen reader so
14
break a WCAG 2.2 Level A or AA criterion
54
links inside article text, listed but not counted
Wikipedia Explore feed from the scan, with numbered boxes on the elements that have issues
The three patterns
9 issues
Search bar and field 36 dp tall
Give the search bar and field a 48 dp touch height.
6 issues
Selected tabs that don’t say so
Give the feed tabs a tab role and selected state.
6 issues
Icon buttons under 48 dp
Widen More options and the scroll button to 48 dp.
Illustrative preview of one build of Wikipedia (Android App) for Android, scanned 22 Oct 2026. Not a full audit.
Section 1

Where the issues are

Confirmed issues on
28
of the 37 screens the scan reached
Of 36 confirmed issues,
21
come from three patterns

The scan reached 37 screens of Wikipedia’s Android app, an alpha build, before it was stopped at 21 minutes. Iris, Genie and Pax checked each one.

They reported 104 findings: 85 from Iris and 19 from Genie. 36 were confirmed and 68 were judgement calls. Nine screens had no confirmed issues; seven had no findings.

Reading articles holds 9 confirmed issues and search 8. The same search bar, scroll button and feed tabs repeat across screens, so each is one fix.

Exhibit 1
The same few components repeat across every journey
Confirmed issues on each screen, by journey. Select a screen to see its findings.
Reading articles· 9
Contents· 6
Search· 8
Explore feed· 7
Onboarding and settings· 6
confirmed issuesjudgement calls onlyclean
Exhibit 2
Every finding was reviewed before it reached this report
Findings by review verdict, number of findings (104 reported: 19 by Genie, 85 by Iris)
36 confirmed issues68 judgement calls
Source: Aucert scan of Wikipedia (Android App) for Android, 22 Oct 2026 (scan_7g7x8jhdauxub86); Aucert analysis
Section 2 · Two screens up close

Up close

Search

Exhibit 3
3 confirmed issues: a short search field and the “EN” button
SCREEN-19, where people search Wikipedia, numbered for this report
Search screen with two numbered boxes marking the elements that have issues
Iris· Accessibility
ConfirmedJudgement call
1
Search field
285 × 35 dp; Android asks for 48 dp
2
Language button “EN”
48 × 36 dp; Android asks for 48 dp
Named “Wikipedia languages”, so saying “EN” to voice control misses it
Pax· Google Play policy
–
Store policy (whole screen)
162 Google Play policies checked on every screen; none broken
Box 1What fixing this screen takes
1
confirmed issue cleared
Give the search field a 48 dp touch height.
1
confirmed issue cleared
Give the language button a 48 dp touch area.
1
confirmed issue cleared
Put “EN” in the language button’s name.
Source: Aucert scan of Wikipedia (Android App) for Android, 22 Oct 2026 (scan_7g7x8jhdauxub86), screenshot as captured; Google Play developer policy; Aucert analysis

The Explore feed

Exhibit 4
2 confirmed issues: an unnamed Tabs button and a silent tab
SCREEN-17, the Explore feed, numbered for this report
Explore feed with two numbered boxes on the Tabs button and the Community tab
Iris· Accessibility
ConfirmedJudgement call
1
Tabs button, showing “1”
No name, so a screen reader can’t say what it does
2
Community tab
Selected, but exposes no tab role or selected state
Box 2What fixing this screen takes
1
confirmed issue cleared
Name the Tabs button, e.g. “Tabs, 1 open”.
1
confirmed issue cleared
Give the feed tabs a tab role and selected state.
Source: Aucert scan of Wikipedia (Android App) for Android, 22 Oct 2026 (scan_7g7x8jhdauxub86), screenshot as captured; Aucert analysis
Section 3

Why it happens, and what to fix

The same few problems repeat across screens. Fixing a pattern once, in the shared component or the colour token, fixes every screen that uses it.

Exhibit 5
Three patterns cause 21 of the 36 confirmed issues
Confirmed issues by pattern, with the cumulative share
PatternConfirmed issuesCumulative
Search bar and field 36 dp tall 9 25%
Selected tabs that don’t say so 6 42%
Icon buttons under 48 dp 6 58%
Names that don’t match the screen 5 72%
Icon buttons without a name 4 83%
Intro pages without progress or Skip 3 92%
Grammar and capitalization slips 2 97%
Two prompts at once 1 100%
Exhibit 6
Every failing target is 35–44 dp
Each confirmed failure, against the minimum it misses; green lines are the minimums
Tap targetssmaller side, dp
3 of the 15 are 42–46 dp, within 6 dp of 48.
24 · WCAG48 · Android 16
Box 3A fix plan in three steps
1Now
Give the search bar and field a 48 dp touch height.
Give the feed tabs a tab role and selected state.
Widen More options and the scroll button to 48 dp.
2Next release
Name the Tabs button and the contents scroll button.
Put “EN” in the language button’s name.
Show progress dots and Skip on every intro page.
3Every build
Check new screens: new components bring patterns back.
Re-run the same checks to confirm each fix held.
Source: Aucert scan of Wikipedia (Android App) for Android, 22 Oct 2026 (scan_7g7x8jhdauxub86); Aucert analysis
Section 4

How you compare

Competitor values are placeholders
PLACEHOLDER DATAEvery competitor value in this section is a placeholder that shows the layout, not a measurement of any real app. Wikipedia (Android App)’s own numbers are real. A scan of a chosen competitor’s published app, run the same way, will replace them.
0.78×
Wikipedia (Android App)’s confirmed issues per screen, against the competitor’s PLACEHOLDER
0.41
issues per screen after the three fixes (real), below the competitor’s 1.25 PLACEHOLDER
Exhibit 7
Today and after the three fixes, beside a placeholder competitor
Confirmed issues per screen, lower is better
Wikipedia (Android App) today 0.97
Wikipedia (Android App) after the three fixes 0.41
CompetitorPLACEHOLDER 1.25
Exhibit 8
Issues per screen by type, beside a placeholder competitor
Confirmed issues per screen, by type
Wikipedia (Android App)Competitor PLACEHOLDER
Touch targets
0.41
0.50
Contrast
0.00
0.30
Text in images
0.03
0.25
Labels
0.22
0.20
Box 4How we compare

The competitor is scanned the same way: the same agents and checks, on the same journeys, within the same week.

Until that scan is in, the competitor’s values here are placeholders, and no rank is shown.

The competitor is never named, and no other app is shown.

Exhibit 9
The same journey, side by side: the whole scan
AppScreensConfirmed issuesPer screenSmallest targetLowest contrast
Wikipedia (Android App)37361.035 dpnone failed
Competitor PLACEHOLDER540.844 dp4.1:1
Source: Aucert scan of Wikipedia (Android App) for Android, 22 Oct 2026 (scan_7g7x8jhdauxub86). The competitor’s values in this section are placeholders, not measurements of any app.
Section 5

The standards

Of the 36 confirmed issues,
14
break a WCAG 2.2 Level A or AA criterion
Exhibit 10
14 issues break WCAG 2.2; 16 are Android guidance and 6 design guidelines
Confirmed issues by standard, number
WCAG Level A 14Android guidance only 16Aucert design guidelines 6
Exhibit 11
Where the screens fall short, standard by standard
AgentStandard · criterionWhat it asksResultConfirmedScreensJudgement
Iris, Accessibility agent 1.1.1 Non-text contentWCAG 2.2 · Level A Images that carry meaning have text; decor is hidden Fails 220
Iris, Accessibility agent 2.5.3 Label in nameWCAG 2.2 · Level A The name includes the visible label Fails 220
Iris, Accessibility agent 4.1.2 Name, role, valueWCAG 2.2 · Level A Controls expose a name, role and state Fails 1091
Iris, Accessibility agent Touch target sizeAndroid accessibility guidance At least 48 × 48 dp Fails 151354
Iris, Accessibility agent Role repeated in labelAndroid Accessibility Test Framework Don’t restate the element type in its label Fails 110
Genie, Design agent Navigation and wayfindingAucert design guidelines Every tab has an icon and a label in one style Fails 333
Genie, Design agent CopyAucert design guidelines One capitalization style; no spelling or spacing errors Fails 220
Genie, Design agent Dialogs and interruptionsAucert design guidelines One prompt at a time Fails 110
Not checked by this preview: the iOS app.
Sources: W3C, WCAG 2.2; Android accessibility guidance (developer.android.com); Aucert design guidelines; Aucert analysis
Appendix

Every finding, by screen

36 confirmed issues and 68 judgement calls, grouped by screen. Select a row for the detail, or a screen name to see it.

11
11
11
1
No issues found
1
1
No issues found
1
1
1
No issues found
No issues found
11
12
1
2
3
31
17
21
No issues found
116
2
No issues found
11
1
21
117
11
1
11
1
11
11
13
No issues found
The # column matches the numbered boxes on the annotated screenshots.
Source: Aucert scan of Wikipedia (Android App) for Android, 22 Oct 2026 (scan_7g7x8jhdauxub86)

Wikipedia (Android App) Android app review

The formatted report is the 13-page PDF: use “Download PDF” on the page, or open Wikipedia-Android-App-Android-app-review-Aucert.pdf beside this page.