Limitations
- Opened PDF files limit
RICOH Accessibility Designer can only work with one PDF document at a time.
See FILES from RICOH Accessibility Designer User`s Guide for more information on the list of PDF documents.
- Table template limitations:
- Multiple cells selection to change cell type not supported: table row data, table row header or table column header.
- Merge cells feature not implemented.
- Variable table cells with more than one line of text not supported.
See Table Template from RICOH Accessibility Designer User`s Guide for more information on how to customize table elements.
- Unmarked text for Block Lines elements
The elements
Block LinesandBlock Lines Paragraphdo not mark all the text if the text is not fully contained in the bounding box of the text contained within the selection box.See Matching Text Elements from RICOH Accessibility Designer User`s Guide for more information on how to use block lines.
- Macros limitation
Macros that contain
Textdirectly underListBodyare not marked correctly, asListItem Bodydoes not have text property.For more information, see Macros from RICOH Accessibility Designer User`s Guide.
- Repeating group limitation
Exiting/breaking repeating group from within a condition branch not supported.
<Action when="false"> <ExitRepeatingGroup/> </Action>
- Allowed writing systems
The only writing system currently supported is left-to-right and top-to-bottom. Any other language that has a different writing systems, such as right-to-left (Arabic or Hebrew) or bottom-to-top (Traditional Chinese or Vietnamese) is not supported yet.
- Font related
- All code points must encode a single character. For example, a codepoint of 2 bytes coding 2 chars.
- Certain fonts with mixed single byte and double byte characters are not supported.
- Annotations are not supported in RICOH Accessibility Designer.
- RICOH Accessibility Designer does not support:
- forms
- JavaScript
- media (sound/video)
- optional content is always flattened (becomes non-optional)
- Tags
- Tags related to Asian languages are not implemented. For example,
RubyorWarichu. - Missing tags:
Formula,Quote
- Tags related to Asian languages are not implemented. For example,
- RICOH Accessibility Designer and PDF2PDFUA do not handle embedded files.
- Existing PDF tags are removed before tagging.
- Text content as an image is not supported, there is no OCR support.
- PDFs with password protection are not supported.
- PDF actions are not supported.
- All fonts must be embedded.
- Table row operators limitation
- You can only use the operators Get Next Row Y and Get Next Row Height within a table.
- List items Join match ID limitation
- Using more than two list items in a list with the same Join match ID non-empty value is not supported.
- Variable rule expression limitation
- To change the value of a variable rule to an expression, you need to use the Edit functionality and not set it from the Variable Value property.
- Macro definition debugging limitation
- Using breakpoints and debugging on rules inside macro definitions is not supported.
- Automatic rule creation (prototype) limitations:
- Supports only
Paragraph,Heading,Block Paragraphs,Figure(raster and vectorial), andTablewith its child rulesTable Row,Table Data,Column Header, andRow Header. Other rules are not supported. - Generated rules for a page are placed in a
Conditionrule named Page followed by the page number. Page condition rules are placed inside aRegionrule named Autodetect followed by a sequential count. - Rules are sorted top to bottom by Y position, then left to right by X position for rules on the same line. This order might not match the intended reading order and needs to be verified.
- Generated rules have
Export Asset toFixedfor X, Y, width, and height. The rootRegionrule has these values set toAbsent. Rules following variable-length content might be positioned incorrectly on other documents. - Vectorial lines, based on maximum X/Y size, do not generate rules.
- Raster images with overlapping centers are merged into a single
Figurerule. - Intersecting raster images are merged into a single
Figurerule when the overlapping area exceeds the configured X/Y tolerance. - Tables are generated first from vectorial line intersections, then from table-text detection. Some tables might not be recognized correctly depending on the drawing style.
- Table-text detection requires every cell to contain text. Empty cells prevent recognition, and non-table text might be misidentified as a table.
- A table is generated only when the row count and column count are both 2 or greater.
- No alternative text is generated for any rule. Alternative text for figures, including logos and text-only images, needs to be added manually.
- Only bold text chunks are detected as
Headingrules, and no heading level is set. - Each page is processed independently, and the feature does not reuse structures detected on other pages.
- Only the currently open PDF is processed.
- Running automatic rule creation regenerates rules for the entire document each time and does not account for existing rules or previously matched items.
- Rotated text, rotated content, or a rotated page is not supported.
- The automatic rule creation button has no keyboard shortcut and cannot be configured in application settings.
See Automatic Rule Creation from RICOH Accessibility Designer User`s Guide for more information.
- Supports only
- Expression Builder number format limitation
Inline expressions in the
Expression Buildersupport only numbers in US locale format.
For more information on RICOH Accessibility Designer, see the User's guide.