Skip to main content

Search

Insert a Table in the Editor Widget

Feedback About the Article

Let us know what was helpful or not helpful about the article below.

2 comments

  • Inna Young

    This article, if I understand it right, is very confusing - on multiple levels. You said: 

    • You may use the Table Insert tool in the Editor Widget instead of the Table Widget. The Table Widget is a fairly simple tool, meaning it is not as robust as the Table Insert tool in the Editor Widget, as described below.

    The Table Widget might not be robust enough, but it produces tables that are in compliance with the mobility, accessibility and usability. It is EVERYTHING that the Editor Widget Table is NOT. Yet, you recommend to use it. I ran it by the CivicPlus support and they went even step further than you did - they strongly recommended to use the Editor Widget Table, implying that the Table Widget will be removed from the system soon. This has prompted me to write a reply. Let's look at it from all three prospective - mobility, accessibility and usability. 

    Let's start with the Editor based table. Here is how it looks on a desktop. We can observe seven columns and multiple rows: 

     

     

    And here is how it looks on the phone (in this case it's iPhone 13 Pro Max). We can observe only five columns, so we would have to do horizontal scrolling and we'd do it ONLY if we know there is something else in this table we need to see. 

     

     

    So, in this case, the usability and mobility (responsiveness to the screen) are NON-existent. When I turned on the screen reader, the reading didn't make much sense either - it would read as if a blind person somehow memorized the all the headers and knows exactly what it means when they hear for example, this line: 

    Banneker Lane - City - Yes - City - Friday

    This makes the narratives completely meaningless. So the accessibility part for this table is missing in action as well. The widget failed to render a table that is  mobile, usable, accessible. 

     

    Now for the comparison, let's observe a table built with the Table Widget.

    Here is that table on the desktop screen - looks fine and all the seven columns are visible:

     

    Let's observe the same table - how it looks on the phone.

     

    We can observe here that the table has realigned itself to the screen and NO horizontal scrolling needed. Here is our usability and mobility in action. But, also, each value is displayed with a CORRESPONDING HEADER. And that's exactly how the screen reader reads it: it names the street and then it goes on naming the attribute (header) + value (cell data). The whole text to speech makes perfect sense, just as it should when a web page is in compliance with the accessibility requirements. 

    The key here is to take your time and actually LISTEN to the screen reader - if it makes any sense at all. Only then we can claim that the web page and the table on it are accessible. I certainly do hope that CivicPlus will NOT remove the only widget (Table widget) that is in compliance with the table accessibility, mobility, usability.

    1
  • John Lanza

    Can Civic Plus respond to this post from Inna Young? It was also suggested to me by Tech Support to NOT use the table widget, but rather create a table within the Editor widget. But as Inna pointed out, the Table widget seems to work better and seems to be better with accessible compliance.

    0

Please sign in to leave a comment.