Merchants assume a single ring size number converts the same way across US, EU and UK systems, and this reference settles what a size chart page needs to carry and why accessibility gaps on that page are the more common failure.
Most people searching for a ring size chart expect a single clean table that maps US numbers to EU and UK sizes with no ambiguity, and the real problem is not the conversion math, it is that the page carrying that table is often built in a way that fails basic readability and accessibility checks before a shopper even gets to the numbers. This reference does not carry a sourced conversion table, because no measured conversion dataset was available, and it will not invent one. What it does cover, using only measured facts, is what tends to go wrong on the page that hosts a size chart and how a merchant checks for that.
The numbers here come from WebAIM’s Million project, an accessibility analysis run across one million homepages and loaded on September 9, 2026. Across that measured set, WCAG conformance sits at 95.9%, up from 94.8% in the prior measurement, which means the share of homepages passing basic accessibility checks improved but did not reach full coverage. At the same time, the number of detected errors across the same set increased by 10.1%, so improvement in the conformance percentage and a rise in raw error counts happened together, which suggests more pages are being built and more of them carry new defects even as more of them also pass basic checks. A ring size chart page, being a fairly simple content page, is exactly the kind of page that inherits whichever defects the rest of the site carries.
Low contrast text appears on 83.9% of the homepages measured, which is by far the largest defect category in the dataset. A conversion table with three or four columns of numbers is especially vulnerable to this because designers often use light gray borders or muted text colors to keep a table looking clean, and that same styling choice is what fails a contrast check. If a shopper cannot distinguish a US size 7 from a US size 9 because the row separators are too faint, the accuracy of the underlying conversion numbers stops mattering.
Missing form input labels show up on 51% of the homepages measured, and this matters directly for any ring size selector built as a dropdown, radio group, or text field on a product page. A field without a bound label can look fine visually while being unusable for anyone relying on a screen reader. Separately, missing alternative text for images affects 53.1% of homepages measured, which matters if the size chart itself is published as a static image rather than a coded table. An image-based chart with no alt text delivers nothing to a screen reader user and nothing to a search engine trying to index the conversion values.
| Defect measured | Share of homepages affected | Risk to a size chart page |
|---|---|---|
| Low contrast text | 83.9% | Table rows and borders become hard to read |
| Missing alternative text for images | 53.1% | Image-based charts deliver nothing to screen readers |
| Missing form input labels | 51% | Size selector fields become unusable for screen reader users |
| Overall WCAG conformance | 95.9% (up from 94.8%) | Most pages pass basic checks but a measurable share still fail |
Shopify’s own guidance on ecommerce conversion benchmarks, read from its blog on September 9, 2026, recommends segmenting orders by price range, for example under $50, $50 to $200, and above $200, rather than relying on one sitewide conversion number. A ring size chart page sits upstream of that calculation: if 1,000 visits land on a product page and 50 of those visits lead to an order, the conversion rate is 5%, and a broken or unreadable size chart is one of the quieter reasons a visit fails to become an order. Browser compatibility is a much smaller concern for this kind of page, since Samsung Internet accounts for 0.614% of tracked usage and every other browser outside the named ones totals 0.467%, so a size chart built with standard HTML and CSS will render correctly for nearly all traffic.
Check the size chart page itself for contrast and label bindings before touching the conversion numbers, since the measured defects above are more common and more fixable than any dispute over the numbers themselves. If a verified US-EU-UK conversion table becomes available from a sourced standards document, add it as a coded table rather than an image, and test it against the same contrast and label checks described here.
This reference does not carry a verified numeric conversion table sourced from a jewelry standards body, because no such measured fact was available to draw from. What can be said is that any conversion table published on a product page needs to be checked for the same accessibility issues that affect size charts generally, including low contrast text, which the measured homepage set shows at 83.9%. A merchant publishing a conversion chart should treat the table itself as a piece of content that needs a real HTML table markup, not an image, so screen reader users and search engines can both parse it. Until a sourced conversion dataset is available, treat any chart you build as a formatting and accessibility problem first.
The most common cause across the measured homepage set is a missing form input label, found on 51% of pages checked. If a ring size dropdown or text input has no label element or aria-label bound to it, screen reader users cannot tell what the field is for even if sighted users can read a placeholder. This is a coding fix, not a design one, and it applies to any product option field, not just ring sizes. Fixing it does not require redesigning the chart, only binding the existing label text to the input properly.
Yes, and it is the single largest defect category measured, present on 83.9% of the homepages checked. A size conversion table often uses light gray text on white backgrounds or thin borders that fail contrast tests, and that is a readability problem for a table full of similar-looking numbers across three columns. The fix is a contrast check on the actual table styling, not a redesign of the conversion values.
A real HTML table is safer given that 53.1% of homepages checked are missing alternative text for images. If a size chart is published as an image and that image has no alt text, screen reader users get nothing and search engines cannot index the numbers inside it. A coded table avoids that failure mode entirely and also makes the numbers copyable and searchable.
Browser share data shows Samsung Internet at 0.614% and an aggregate Other category at 0.467% of tracked usage, so a size chart page mostly needs to work in mainstream browsers rather than edge cases. The bigger risk for a size chart page is not browser compatibility but the accessibility defects already measured across homepages, including the 10.1% increase in detected errors site-wide.