To read is to
to look at words or symbols and understand what they mean
in which sense no machine has ever read so much a jot or tittle yet, unless you are willing to be broad with your definition of "understand",
to understand and give a particular meaning to written information, a statement, a situation, etc.:
That is, I mean to say, reading is a peculiarly human activity in the first place, and the distinction between human- and machine-"readable" data is one that has gotten a lot of attention in the last hundred years or so. Still, the only one-word answer that I know is hyphenated: "human-readable"! It is used mainly in the context of computer-related information, like on softwareengineering.stackexchange but it can also be used for legalese translated to layman's terms.
Eric S. Raymond's compilation at catb.org says:
[very common] In reference to software, source is invariably shorthand for ‘source code’, the preferred human-readable and
human-modifiable form of the program. This is as opposed to object
code, the derived binary executable form of a program. This shorthand
readily takes derivative forms; one may speak of “the sources of a
system” or of “having source”.
There is also a verb for making some kind of otherwise obscure data more accessible to the human glance:
prettyprint: /prit-ee-print/, v.
1. To generate ‘pretty’ human-readable output from a hairy internal representation; esp. used for the process of grinding (sense
1) program code, and most esp. for LISP code.
2. To format in some particularly slick and nontrivial way.
Another option, that I just now found in an answer at this (very similar) ELU Post: antonym for machine readable data, is "un-structured data" (vs. "structured" or "formal".