- Experiment with API technologies like [DisplayID](https://en.wikipedia.org/wiki/DisplayID) and [RawDpi](https://learn.microsoft.com/en-us/uwp/api/windows.graphics.display.displayinformation.rawdpix) for working with actual physical size and resolution, even if it’s beyond the context of typical web browsers where they aren’t supported yet.
- Try setting font sizes according to internal font measurements like x-height, and/or even more complex [fluid sizing calculations](https://css-tricks.com/simplified-fluid-typography/) based on a variety of interrelated factors.
- Submit or support [feature requests](https://github.com/w3c/csswg-drafts/issues/614) for app developers and standards organizations to improve functionality for working with sizes based on physical measurements and/or internal font metrics.
-- Get more comfortable thinking about [viewing distance and angular units of measure](https://sizecalc.com) when calculating type sizes.
+- Get more comfortable thinking about [viewing distance and angular units of measure](https://web.archive.org/web/20240505051650/https://sizecalc.com/#distance=15inches&perceived-size=343.488627arcminutes&physical-size-units=points) when calculating type sizes.
- Be more observant about how different typefaces may require changes in size specifications due to differences in their design or production.
- Perhaps more important than anything, test the sizing logic on a variety of screens and devices to ensure it works reasonably well in as many environments as possible.