The current styling of the webpage was not designed with mobile browsing in mind (and it wasn't even checked on a mobile browser), but that doesn't mean it can't be. If the small-window view gave the last column more space, would that be sufficient to address your concerns?

If not, do you have any suggestions for an alternative presentation? We want the table (or whatever replaces it) to be relatively dense, so that people can get a quick understanding of the criteria and then click through to the one they want more details on.

What about something like this?

OSPS-EX-01  1  Example
     Examples MUST NOT use lorem ipsum because Latin gibberish is still gibberish.
OSPS-EX-02  1  Example
     Examples must use domain names reserved for that purpose as described in section 6.5 of RFC 6761

I agree with the visibility/usability checking we need to do prior to going live. The spreadsheet/table-style of organization has its place within our collateral, but probably shouldn't be the main person-readable method. A next step we have is once the control mappings are agreed upon, we feed that info back into the yaml file. We've briefly chatted about "the spreadsheet" and how that data can be presented. I certainly have no desire to try and build the table again in markdown and the info can't exist in a gsheet forever. I'd love to hear some conversation on how we might display the control-mapping information more clearly and simply.

I think what you want is a "responsive table" - that is, the formatting radically changes when you have a narrow screen so it's still readable by breaking it differently. Unsuprisingly, there are many ways to do this. A few links:
https://css-tricks.com/responsive-data-table-roundup/
https://codepen.io/shellbryson/post/responsive-tables
https://github.com/rootwork/responsive-tables-builder (links to some options)

We should look at options, and then apply it.

@SecurityCRob we do have spots in the current template (and yaml) for control mappings!

Of the things we've discussed so far, I think trying a responsive table approach (in addition to being as terse as possible with the criteria) is the best approach. We can do it now or I can do it later this week as part of the more general web-rearrangement I want to do.

I've been experimenting with a <div> based approach that almost, but doesn't quite work. But I think I've stumbled upon a better option. I should have some time on Monday to clean up my mess and share it with the group.