|
POST
|
Hi Don, I'm not sure I can accurately visualize your problem. Are you talking about the Dataset Card description? It currently justifies text and truncates by character count. It doesn't support HTML input. The only card we have that supports HTML input would be our current text card. If you're comfortable with HTML, you can use code snippets from this page to generate a card, Calcite Bootstrap. However, we have added a lot of improvements to our Gallery Card. From the Gallery Card, you could do manual selection for datasets you wish to feature and while we do not support HTML input in this card either, there are more styling options. Or you can choose the dynamic option and use tags and/or groups to filter down to the content you wish to highlight and that content would be centered by default. Klara
... View more
12-21-2018
07:35 AM
|
0
|
1
|
650
|
|
POST
|
Hello Niklas, Our video player card intentionally does not support autoplay because we're striving to make our product more accessible all around. It is considered a jarring experience to arrive on a page, especially if you're using assistive technology like a screen-reader, and hear audio already playing somewhere on the page. It's akin to opening a site and hearing background music that makes it hard for you to focus, except you don't actually know where on the page the controls to turn it off might be. For more information on why autoplay is not considered a best practice in terms of usability, you can read https://a11yproject.com/posts/never-use-auto-play/ (There are additional resources at the end of the article that further explain why automatic motion isn't the best experience for several audiences and why.) Klara
... View more
12-21-2018
06:02 AM
|
0
|
0
|
1008
|
|
POST
|
Hi Kevin, We can look into improving this. This section of the app is a little bit older than other parts. The tricky bit is that we do have a number of customers using the old standard thumbnail size, which was a maximum resolution of 200x133 pixels. I think we can bump the aspect ratio up to ~1:4 in the short term and then map to the new standard during some improvements coming out early next year. To answer your question on why there is a gray background? If one does not include a thumbnail with their item, we load a default thumbnail in and that is a white image with a transparent background. We were using the background color of the site, but then sometimes the white image would vanish on white sites. Gray was the most neutral for the largest array of customer themes. This whole area could use a little work, but there are several major features ahead of it. I'll keep you posted.
... View more
11-27-2018
05:56 AM
|
2
|
0
|
593
|
|
POST
|
Hello, Can I recommend you switch your cards to our new suggested format? You can find code examples here: Calcite Bootstrap The code you are currently using was deprecated within the framework because it was neither mobile friendly nor accessible to keyboard users. The good news is that you can update your text cards containing the HTML using new style and all the CSS will automatically be applied. The updated cards are responsive and should help you achieve your goal of a mobile friendly site.
... View more
10-11-2018
05:32 AM
|
0
|
0
|
620
|
|
POST
|
Hello Tom, I wanted to let you know that our latest release added the feature that you had asked about. You can now upload an image onto a row and then under the appearance settings for that image, set whether or not you want the background scrolling to be present. By default it is off and you would have what you have today, but if you turn it on, we will fix the background image (no CSS required) within the row and scroll content over top the image. Hope this makes things easier for you in the future!
... View more
10-10-2018
09:56 AM
|
0
|
0
|
1368
|
|
POST
|
Speaking for Calcite Bootstrap, we are reluctant to include a carousel feature as studies have proven they are not an effective user-experience. The Nielson Normon Group (UX research firm) concluded in a study they performed that users skip over carousels and accordions that auto-rotate, and a B2B company called Search Engine Land determined that sliders can negatively effect your SEO as they provide redundant headings, can slow page load, and often provide shallow content lacking keywords. Their study also suggested it doesn’t matter what content is in the carousel (branding, service links, white papers) the click-rate remains low. In addition, carousels and sliders can prove to be a hinderance for organizations that care about web accessibility, WCAG 2.0, or Section 508 compliance. Carousels are difficult to build in a way that is compatible for assistive technologies as they incur issues with keyboard navigation, relaying semantic relationships between content, and any automatic movement requires stop/pause/hide controls, so sites that include a carousel are likely to be making it more difficult for visitors with disabilities.
... View more
08-16-2018
08:31 AM
|
2
|
3
|
2495
|
|
BLOG
|
Update: David Watkins from ArcMap tells me that ArcMap does allow you to author maps/basemaps and choose, colors, fonts, sizes, etc., which provides the tools needed to make a high contrast map and avoid color combinations that would be trouble for someone with color blindness. He also suggests using Color Brewer http://colorbrewer2.org/#type=sequential&scheme=YlGnBu&n=7 to find options that are safe for audiences that are colorblind. So while it is possible to use Acrobat to solve these issues from inside the PDF, it may be easier to do it correctly from inside ArcMap before you export. A month or so ago, we got a question from a customer on how to make an exported ArcMap map PDF accessible. In this post, I am going to cover how to make a PDF accessible using Adobe Acrobat Pro. There are many tools that assist in making PDFs accessible; however, I will be focusing on Acrobat because it is the tool I have personally used the most often. Full Disclaimer: I have never used ArcMap. But I have made some 500+ PDFs accessible and a colleague has kindly provided me with a simple map PDF to use as a walk-through for purpose of this post. I will touch upon more complex map PDFs at the end. Now before I begin, I want to lay out a few idiosyncrasies with Acrobat: 1) There is no undo option - If you screw something up, your best course of action is to exit the file without saving changes and reopen it. This means that you must save frequently as you correct issues. This is especially important when you are tagging a document and setting reading order. 2) In my experience, Acrobat is likely to crash while doing Reading Order on large files. Therefore, if your document is larger than 5 pages, I'd recommend dividing it into 5 page sections, doing accessibility on each section, and then merging them all together at the end, before setting a title. Turning on Accessibility Tools Open your PDF file in Acrobat and check to see if you have the Accessibility option in your sidebar. If you don’t see it, go to Tools and search for “Accessibility," then click Add. Select Accessibility from the sidebar menu. You should now be in the Accessibility tools interface. Select Full Check from the Accessibility Tooling Pane, then select Start Checking from the modal. The Accessibility Checker will produce a list of issues that can be expanded within it’s side panel. It may be tempting to right-click an issue and select Fix, and this can be safely done for things like title or language, but should be avoided for issues involving tag structure. (If you don’t know how Acrobat “fixed” the issue behind the scenes, then don’t use the automatic option.) Fixing Document Issues Skip anything that says Tagged PDF - Failed and/or Reading Order for now and start with the Primary Language - Failed and Title - Failed issues. For Language, right-click, and select Fix. Acrobat will launch a dropdown menu that you can use to make a selection, then select OK. For Title, right-click, and select Fix. Acrobat will launch a modal, and you may need to unselect the Leave As Is checkbox in order to type a title into the title input field. Then select OK. Save For issues that say Needs manual check, you will have to apply accessibility guidelines by your own knowledge as Acrobat cannot validate them automatically. For example, if I were to check for appropriate contrast of the red symbols on my light green neighborhood map, I would do the following: Screenshot a bit of the image, open the screenshot in a browser, use a browser extension called Colorzilla to pull the colors out of the image (available for Chrome and Firefox), and then paste those two colors into WebAIM’s color contrast checker. WebAIM shows that the red used for the hospital marker is not sufficient contrast against the map background. However, the black text and purple metro lines are fine. While a bit tedious, it is possible to correct the red hospital markers from inside Acrobat. Select a marker on the map, use your cursor to highlight it, then go to Tools > Edit PDF. This will open the Format sidebar, wherein you may select a more appropriate color. Once finished, right-click the “Needs Manual Check” item and select Pass to indicate that you’ve reviewed the item and if necessary, made changes. Now Save. ...Anddd Acrobat froze. Good thing I just saved everything. (If this happens to you, you’ll have to rerun the Full Check to open up the Accessibility Checker report panel.) Fixing Page Content Issues For Tagged Content - Failed issues, you’ll need to do some manual tagging to resolve them. If you don’t have an icon for the Content pane visible in your Accessibility Checker, then select Autotag Document from the Accessibility Tooling Pane. This will produce a report, and add the Content icon to the opposite side. Under Content, right-click an artifact and select Show in Tags option. This should add an icon for the Tags pane. Now that you have all the components you need in your workspace, I’d actually recommend you delete all the tags in the Tags pane that got added during the Autotag Document step. With the Reading Order pane open, right-click your PDF, and select Clear Page Structure. Autotagging is a bit like alphabet soup - it’s hard to comprehend and takes a longer time to fix than doing it from scratch. Once you’ve deleted your tags, you’re read to begin. Open the Reading Order tool. This will open a modal with a lot of disabled buttons. Under the Show Page Content Groups checkbox, select the Structure Types radio button. This will indicate what type you have tagged certain groups of elements. With the Reading Order modal open, draw a rectangle around the title text. Select the Text/Paragraph button. Repeat with other text elements on the PDF. For image elements, tag Figure. Right-click a Figure tag to select Edit Alternative Text. In the dialog that opens, describe the information conveyed by the figure, and select OK. Weird Mysteries What should you do when you draw a rectangle around some element to tag, and Acrobat highlights a block of what looks like empty space? Do not tag it to make it go away. The correct action is to delete the empty artifact. Open the Content pane. Navigate through the container artifacts, until the offending one becomes highlighted. Drill down into the artifact to the root issue, in this case, a text element containing nothing. Right-click the Text element and select Delete. Save Fixing Alternative Text Issues Now honestly, you’ll have probably fixed most of these issues while doing manual tagging. Run Full Check again or right-click the Alternative Text accordion from the report and select Check Again. I have one figure left that I tagged, but forgot to add alternative text. In the Accessibility Checker report, select any errors to see them highlighted on the page. Then in Accessibility Tooling Pane, selection Set Alternative Text. Acrobat will scan the PDF for all images that it thinks need alt text. For each figure missing alt text, Acrobat will highlight it, and prompt you for a description. You can use the arrows in a dialog to move through all figures with alt text. Then Save & Close. Fixing Reading Order Issues Finally, you come to reading order. This is the least fun part of the whole process, but probably the most important. Yay you! What you want to do here is order all the artifacts in the Content Pane, top to bottom, the way you want a screen-reader to encounter them in terms of reading order - almost as if they were a numerical list. Open the Content pane. Save everything you’ve done up unto this point. Drag and Drop each element container to the correct position. Wrapping Up Do one last Full Check, delete any empty tags, and you’re done! What does deleting empty tags look like? If you click on an element under Page Content > Tagged Content - Failed, and it highlights part of the PDF that is empty, right-click the element and select Show in Content Panel. Once there, find the empty element and delete it. Then rerun Full Check. One Last Note... If you have a PDF that is very complicated visually, uses lines instead of points, or has multiple layers of complex data, and you’re finding it difficult to tag, I attended a Section 508 panel where Rob Haverty from Adobe shared a best practice on making complex visual PDFs accessible. He recommended using the Reading Order pane to divide the map into Figures, which can then utilize Alternative Text to describe what is occurring visually at a high level.
... View more
07-19-2018
01:50 PM
|
7
|
8
|
13898
|
|
POST
|
I'm afraid I may not have very good advice as I'm a little vague about the end-goal, but if your wish is to have the burger menu appear on the left, you'll want to create a unique class on the navigation root element and that'll help you float the menu to the left. If your goal is to have a single button outside the menu and always on the right, I would use the .pull-right class rather than .navbar-right as there's some extra styling attached to .navbar-right because we need it a little different. You'll want to move your "FR" button to the top of the nav container, so that it has some static content to float around and into the correct position, and to avoid having it part of the collapsable menu. Per your logo, if you use a custom-class you can remove the padding that gets generated by the navbar-brand class. I, unfortunately, was not able to remedy the burger menu being flush left with the edge of the screen since it has something to do with the negative margins in navbar-header, but I couldn't find the appropriate set of selectors that would cause an override. You may need to experiment a bit more. Finally, I added a clearfix class in an empty div at the bottom to make sure none of these floats caused any other mischief. CSS .left-menu .navbar-toggle {float: left; background-color: #101012;}
.left-menu .navbar-brand {height: 70px; padding: 5px 0px;} HTML <nav class="left-menu navbar navbar-default">
<ul class="nav nav-navbar pull-right">
<li>
<a href="#" class="btn btn-primary" style="margin-top: 5px; margin-right: 5px;">FR</a>
</li>
</ul>
<div class="container-fluid">
<!-- Brand and toggle get grouped for better mobile display -->
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1" aria-expanded="false">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a href="http://opendata.arcgis.com/" class="navbar-brand">
<img src="https://maps.ottawa.ca/od_images/Ottawa.png" alt="City of Ottawa Logo">
</a>
</div><!-- /.navbar-header -->
<!-- Collect the nav links, forms, and other content for toggling -->
<div class="collapse navbar-collapse" id="bs-example-navbar-collapse-1">
<ul class="nav navbar-nav">
<li><a href="#">Home</a></li>
<li><a href="#">Apps</a></li>
<li><a href="#">Data</a></li>
<li><a href="#">Stories</a></li>
<li><a href="#">Feedback</a></li>
</ul>
</div><!-- /.navbar-collapse -->
</div><!-- /.container-fluid -->
<div class="clearfix"></div>
</nav>
... View more
05-17-2018
01:55 PM
|
0
|
0
|
2336
|
|
POST
|
Hi Tom, Presently, we do not support fixed background images. All row background images use the responsive CSS property of `background-size: cover` and the default scroll state for the `background-attachment` property. We do have an issue slated to add a control that would allow you to set `background-position` which allows you to center the focal point around which your image will responsively resize and we may be able work `background-attachment` in during that time. But unfortunately, there isn't a very clean way to do the CSS to override it as-of-today since none of the rows have unique classes on them and you should not use the dynamic ember IDs as those change.
... View more
04-09-2018
11:00 AM
|
0
|
0
|
1368
|
|
POST
|
Hi Julie, This is a very weird situation. From a technical standpoint, nothing inside the iframes should be scrollable because the iframe parameter that sets scrolling is currently set to not allowed in all browsers. I have observed that any content I iframe in that is not a survey, does not scroll. Now we get to the really odd part. Certain surveys seem to support inline scrolling. The survey that I was able to scroll when I tested it out earlier is a 5.2.3 version survey that I created this past November; however, when I created a brand new survey today, I have the exact same issue as you in that the survey does respect the iframe parameter. I'm guessing that your colleague may have created their survey a little while ago too and that's why they were able to scroll. So unfortunately, this leaves us at my first response. It is currently unsupported and your colleague got a lucky window in survey versioning where this somehow got supported and overrode browser defaults (a happy bug.) But we do have an issue on our backlog to allow this parameter to be customizable so that - for example in your case - you could set it to allowed.
... View more
04-06-2018
01:10 PM
|
0
|
1
|
3359
|
|
POST
|
Hi Julie, So I took a look at the site you provided and tested out my own survey, which I added into a site through an iframe and I was actually surprised to discover that all the browsers we support (Firefox, Chrome, Safari, IE11, & Edge) were ignoring the parameter that sets the iframe not to scroll and scrolled the survey content regardless. I believe the survey team may have implemented something on their side, since our card is still blocking the parameter. Have you tried your site recently to see if the survey would scroll?
... View more
04-05-2018
01:19 PM
|
0
|
3
|
3359
|
|
POST
|
Hi Julie, Do you have a public view of the page that your colleague has that on? What browser were they using? It may very well be that certain browsers ignore the parameter and do their own thing, but I would be curious to dig in and see if it was a CSS solution.
... View more
03-30-2018
12:49 PM
|
0
|
5
|
3359
|
|
POST
|
Hi Julie, Presently, there is no way to set scrolling on iframes and you do have to adjust the height manually. Setting the scroll parameter on iframes is deprecated functionality according to web standards. However, modern browsers haven't lived up to the CSS options, so we're hoping to get the functionality added in the next couple months, as like you, others have also made this request. Thanks
... View more
03-28-2018
09:53 AM
|
0
|
7
|
3359
|
|
POST
|
Hi Krystal, If I might offer a suggestion...I know the code above that you provided is part of the default site template. While we still support that type of card, it is our goal to update new site templates to use a more accessible, more mobile-friendly version of cards for which support is already included in our codebase. While you may be able to achieve your desired look by overriding the width of the cards in the .cards-list .card class with inline or embedded styling, I would encourage actually using this code instead: http://esri.github.io/calcite-bootstrap/patterns.html#card-classic which will automatically resize your card to fill the whole space. Then you wouldn't need to center the card and could instead add a margin to your text.
... View more
03-28-2018
09:38 AM
|
0
|
0
|
1616
|
|
POST
|
You are correct. We do not support @import for files on your local machine, and at this time, you can only set two default fonts (body text, heading text) and not the iconfont. If the municipality had a license for Arial or Helvetica, it's possible they have a webfont URL, but it's also possible that they are banking on everyone having either Helvetica or Arial on their computers. You could use Roboto though since it's in Google Fonts, since it is part of their fontstack, they may be fine with the site using it by default.
... View more
01-23-2018
08:50 AM
|
0
|
3
|
2013
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 04-22-2025 07:38 AM | |
| 1 | 01-30-2025 07:00 AM | |
| 1 | 09-20-2024 05:29 AM | |
| 1 | 08-21-2024 10:31 AM | |
| 1 | 01-12-2023 06:17 AM |
| Online Status |
Offline
|
| Date Last Visited |
9 hours ago
|